The SLOs Status screen displays a list of your existing Objectives and shows how the monitored systems are performing on a weekly, monthly, and quarterly basis.
For each Objective, you will see the following information:
- Test: the name of the Test that this Objective is monitoring, as configured in Test Properties.
- Objective: the name of this Objective, as configured in Objective Properties
- Goal: The percentage goal configured for this Objective
- Weekly, Monthly, and Quarterly performance to date:
- Current: The percentage of uptime/acceptable performance to date within the selected timeframe. This value will be highlighted in green if it is at/above the Goal, and it will be marked red otherwise.
- Budget Spent: The percentage of total downtime/unacceptable performance minutes that the test has used up. For example, if we are looking at weekly performance and the goal is 95% uptime, then the test can log up to 504 minutes of downtime per week without violating the SLO (5% of 10,080 minutes in a week = 504 minutes). If the test has logged 252 minutes of downtime so far this week, then Budget Spent would be 50% (252 / 504).
You can perform the following actions by hovering over an Objective and then clicking the 3-dot menu next to the Objective name:
- View Objective Details (see more information below)
- Edit Objective Properties
- Download SLO data in CSV or .XLSX format
- Delete the Objective
Objective Details
When you select View Details for an Objective, this opens the Details blade.
The Objective Details blade displays the following information:
- Timeframe: Current month by default. You can change the timeframe by selecting new start/end dates.
- Metric: The metric being evaluated for the Objective (Availability or Test Time in milliseconds)
- Goal: The percentage of time that the test must not be in the Violation Condition in order to meet the SLO.
- Current: The percentage of time that the test has not been in the Violation Condition within the selected timeframe so far.
- Budgeted Mins: The maximum number of minutes that the test may be in the Violation Condition within the selected timeframe before violating the SLO, calculated as the total number of minutes in the selected timeframe minus the Goal. For example, if the selected timeframe is one day (1,440 mins) and the goal is 95% uptime (.95 * 1,440 = 1,368 mins) then the Budgeted Mins would be their difference: 1,440 - 1,368 = 72 mins.
- Mins Violation: The number of minutes that the test has been in the Violation Condition within the timeframe so far.
- Budget Remaining: The difference between Budgeted Mins and Mins Violation (i.e. how many more minutes the test may be in the Violation Condition within the selected timeframe.) If Mins Violation is greater than Budgeted Mins, this number will be negative, and the SLO has been violated for the selected timeframe.
- Violation Condition: the number/percentage of nodes/test runs that must detect downtime or unacceptable performance within a configured timeframe in order to start counting against the SLO.