At-a-glance metrics
At-a-glance metrics
Beta: Insights is currently in beta. Share your feedback with your Customer Success Manager (CSM) to help us improve.
At-a-Glance metrics are four key performance indicators that provide a quick health check of Itential Platform or workflow performance.
Where they appear:
- Summary Dashboard: Platform-wide metrics aggregated across all root jobs
- Workflow Details: Workflow-specific metrics filtered to a single workflow
Each metric displays:
- Current value: The metric for your selected time range
- Percentage change (delta): Comparison to the equivalent previous period
- Trend indicator: Visual arrow showing direction of change
Scope:
- Summary Dashboard: Calculates using root jobs only.
- Workflow Details: Calculates based on the Root Jobs / All Jobs (Root and Child) toggle selection.
Metrics
Jobs Run
The total count of jobs executed during your selected time range.
Interpretation:
- Upward trend (▲): Platform usage is growing - automation adoption is increasing
- Downward trend (▼): Platform usage is declining - may indicate reliability concerns, reduced confidence, or seasonal variation
- Stable trend (—): Mature, consistent usage - may signal opportunity to expand automation
Business value: This metric demonstrates Platform adoption and helps identify whether automation is being actively used and growing.
Example scenarios:
Completion Rate
The percentage of jobs that completed versus those that were canceled.
Calculation: (Completed jobs / Total jobs) × 100 Where Total jobs = Completed jobs + Canceled jobs
Jobs can reach completion by:
- Completing successfully through their intended path
- Completing through a defined error transition or failure path
Interpretation: A declining completion rate indicates that more jobs are being canceled before reaching completion. This may signal workflow design issues, timeout problems, or infrastructure constraints.
This metric compares completed versus canceled jobs. Jobs in error or running states are not included in this calculation. This metric measures execution completion, not whether jobs accomplished their intended business outcomes.
Example scenarios:
What to do if completion rate is declining:
Total Runtime
The cumulative execution time of all jobs in your selected time range.
Business value:
- Justifies infrastructure investments when load increases
- Identifies performance degradation requiring optimization
- Validates optimization efforts when runtime decreases with stable usage
- Helps predict resource needs for capacity planning
Example scenarios:
Context is important when interpreting the Total Runtime metric. The following examples interpret the Total Runtime metric within the context of the associated Jobs Run metric.
What to do if runtime is increasing disproportionately:
Time Saved
The cumulative manual effort avoided through automation, not the difference between manual time and automation execution time. The value is in avoiding manual work, regardless of automation speed.
Calculation: Σ(Pre-automation Time for each job)
Interpretation:
- High time saved with green ▲: Excellent ROI and growing automation value
- Low or empty time saved: Pre-automation time not configured for workflows
- Time saved with red ▼: Fewer jobs running or workflows with high pre-automation time executing less frequently
Business value:
- Directly quantifies ROI in hours saved
- Essential for executive reporting and renewal conversations
- Justifies automation investments with concrete metrics
- Demonstrates value to stakeholders in understandable terms
Example scenarios:
If time saved is empty or low:
See Configure pre-automation time for setup instructions.
Use metrics together
The four at-a-glance metrics are most powerful when analyzed together:
Healthy growth pattern
- Jobs Run: ▲ 15%
- Completion Rate: 100% (stable)
- Total Runtime: ▲ 16%
- Time Saved: ▲ 15%
Example interpretation: Platform growing, all jobs completing, delivering value
Workflow reliability issue pattern
- Jobs Run: Stable
- Completion Rate: 95% (▼ 5%)
- Total Runtime: Stable
- Time Saved: Stable
Example interpretation: Some jobs failing to complete - workflow logic or error handling issues need attention
Adoption concern pattern
- Jobs Run: ▼ 20%
- Completion Rate: 100% (stable)
- Total Runtime: ▼ 20%
- Time Saved: ▼ 20%
Example interpretation: Platform usage declining - investigate confidence issues or seasonal factors
