SLA Status % calculation and interpretation in Automation Analytics & Intelligence
search cancel

SLA Status % calculation and interpretation in Automation Analytics & Intelligence

book

Article ID: 445334

calendar_today

Updated On:

Products

Automation Analytics & Intelligence

Issue/Introduction

Users may observe inconsistencies in the SLA Status % calculations within the Jobstream Runs - Grid page.
Specifically, jobstream runs with similar clock-time delays (e.g., both 3 hours late) may show significantly different percentage values (e.g., 337% vs 1035%).

Environment

Automation Analytics & Intelligence (AAi) 24.X +

Cause

The SLA Status % is a relative measure rather than an absolute one.
It expresses how early or late a run finished as a proportion of the time that specific run had available—defined as the duration between the run start time and its SLA deadline.
Because each run can start at a different time relative to its deadline, the 'available window' varies, leading to different percentage results for the same amount of late time.

Resolution

Understand the following logic when interpreting SLA Status % values:

The Formula

The percentage is calculated based on the run's own available time window:

  • Negative (-)%: The run finished early.
  • Positive (+)%: The run finished late.
  • 0%: The run finished exactly on the SLA deadline.
  • 100% Late: The run overran its available window by exactly the length of that window.
  • 1000% Late: The run overran its available window by ten times its length. This typically occurs when a run starts very close to its deadline.

Comparison Examples

Consider two runs that both finished 3 hours after a 02:00 deadline:

  1. 1035% Late: The run started at 01:42 (18-minute window). 180 minutes late / 18-minute window ≈ 1000%.
  2. 337% Late: The run started at 01:00 (60-minute window). 180 minutes late / 60-minute window = 300%.

Best Practices for Monitoring

  • For intuitive tracking: Use the Early/Late column in the grid. This shows the actual time difference (e.g., +03:07:52) without relative scaling.
  • For broad comparisons: Use the SLA Status % to compare runs with widely different available windows on a common scale.
  • To reduce large percentages: Review start times or adjust SLA deadlines, as small start-to-deadline windows mathematically generate higher percentages.