<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Monitoring on Step Documentation</title>
    <link>https://step.dev/knowledgebase/30/categories/monitoring/</link>
    <description>Recent content in Monitoring on Step Documentation</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Thu, 28 Feb 2019 14:08:01 +0100</lastBuildDate><atom:link href="https://step.dev/knowledgebase/30/categories/monitoring/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Measurements and Metrics</title>
      <link>https://step.dev/knowledgebase/30/userdocs/analytics/measurements-and-metrics/</link>
      <pubDate>Thu, 28 Feb 2019 14:08:01 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/30/userdocs/analytics/measurements-and-metrics/</guid>
      <description>Step analytics are built on two complementary data types:
Measurements A measurement is a named, timed observation attached to a plan&amp;rsquo;s execution step. Each measurement captures a name, a duration in milliseconds, a start timestamp, a status (PASSED, FAILED, or TECHNICAL_ERROR), and optional custom attributes (key/value pairs).
Measurements are created automatically by the Step framework for keyword calls as well as for instrumented plan nodes. Custom measurements with finer granularity or enriched attributes can also be defined in keyword code (see Measurements in the Keyword API).</description>
    </item>
    
    <item>
      <title>Dashboards</title>
      <link>https://step.dev/knowledgebase/30/userdocs/analytics/dashboards/</link>
      <pubDate>Thu, 28 Feb 2019 14:08:01 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/30/userdocs/analytics/dashboards/</guid>
      <description>Managing Dashboards: Overview The Dashboard List page provides a straightforward way to manage all your dashboards. This feature simplifies how you handle various analytics dashboards, making it more efficient to work with your data.
Step comes with 4 pre-populated dashboards:
Execution dashboard: used to analyse the performance of a single Step execution Analytics dashboard: meant to be used for schedules performance analysis, also accessible from the monitoring view Executions Overview: tracks per-execution metrics (execution count, duration, failure rate) generated at the end of each execution, giving a historical view of campaign health over time Grid Monitoring: displays agent health and activity metrics; not project-specific and accessible from any tenant Key features: Create: Easily add new dashboards for different data sets or projects.</description>
    </item>
    
    <item>
      <title>Monitoring</title>
      <link>https://step.dev/knowledgebase/30/userdocs/monitoringview/</link>
      <pubDate>Thu, 28 Feb 2019 14:08:01 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/30/userdocs/monitoringview/</guid>
      <description>If you’ve purchased the Monitoring package or are running the Premium Enterprise version of Step, you’ll be able to view the status of your Plans scheduled entries. This is very useful for the purpose of building a monitoring dashboard that would be exposed to a support team.
Monitoring View To open it select Reporting -&amp;gt; Monitoring in the sidebar menu.
Name (2): the name of the Scheduler that is monitored - clicking it opens the schedules execution report Plan Link (3) navigate to the connected plan by clicking on the file icon next to the name Cron Expression (4): the expression used in the Plan scheduling entry Last execution (5): the last executions end date-time - clicking on the date navigates to that execution Last status change (6): the last time the Plan execution overall status has changed (from FAILED to PASSED for instance) Status (7): the last Plan execution status Action: execute (8), edit (9), or analyze (10) the Schedule Select which plans to monitor (1) The Monitoring View displays an entry for each Scheduler, so in order to monitor a plan it needs to have a scheduled execution.</description>
    </item>
    
    <item>
      <title>Analytics</title>
      <link>https://step.dev/knowledgebase/30/userdocs/analytics/</link>
      <pubDate>Thu, 28 Feb 2019 14:08:01 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/30/userdocs/analytics/</guid>
      <description>Step collects performance data — measurements and metrics — from every execution and makes it available in multiple ways:
Execution and cross executions reports: through the charts, statistics tables and embedded analytics dashboards as detailed measurements and metrics list for each keyword execution in the report details Performance and Metric assertions - the collected measurements and metrics are available as well for: Performance Assertion can be defined in plan and assert collected measurements during the execution of the plan Metric Assertion can be used in assertion plan to evaluate the success of schedule over a series of executions Analytics dashboards: standalone dashboards for cross-execution analysis, scheduling health, grid monitoring, and custom investigations.</description>
    </item>
    
  </channel>
</rss>
