View an SRM SLO

Release version: Washingtondc

Updated December 12, 2024

4 minutes to read

View a service level objective (SLO) that you or your team owns. SLOs help you assess a service's health and reliability.

Before you begin

Role required: Responder, Manager, or Administrator

Note:

Administrators can view any SRM SLO.

Procedure

Navigate to Workspaces > Service Operations Workspace.
You are taken to your SRM homepage.
Note:
If you have other SOW applications, and depending on your assigned roles, that homepage may not be the SRM homepage. It is the SOW homepage instead, with SRM alerts and incidents included in your metrics. In that case, to view SRM specific areas, select SRM modules from the left navigation pane.
Select Services from the left navigation pane.
Select the Reliability metrics tab.
Open a Service level objective.
View the SLO header.
The top header contains service information for:
- SLI type:
  Type of the SLI based on which the metrics are calculated. The available types of SLI are as follows:
  
  Availability: Percentage of time your service is available. (Default)
  
  Errors: Measurement of how frequently service error occurs.
  
  Latency: Time taken to service a request. The actual amount of time that elapsed.
  
  Saturation: Measurement of your system fraction, emphasizing the resources that are most constrained.
  .
- SLO Type:
  Type of SLO based on which metric you choose. The available types of SLO are as follows:
  
  Duration: the amount of time the service spends without breaching. It is the only value available.
  Metrics for Duration are as follows:
  
  Objective (percentage): Percentage of the desired SLI performance.
  
  Error budget: Displays, in days and time, how much error budget is left.
  
  Count: Number of occurrences in a given compliance period.
  Metrics for Count are as follows:
  
  Limit (occurrences): Number of occurrences after which a breach has occurred.
  
  Remaining breach occurrences: Number of occurrences left.
- Service: Service associated with the SLO.
- State:
  State of the SLO. Choices are:
  
  Draft: The SLO is not running in your instance yet. You can add new SLIs or update existing SLIs and you can delete the SLO.
  
  : The SLO is active in your instance. You can edit, retire or delete the SLO.
  Note:
  Editing an SLO in the running state retires it and a new copy is created. See Working with Reliability metrics
  
  Retired: The SLO is no longer running in your instance. You can reactive it.
- Reliability: How reliable the service is.
  
  Stable: All SLOs in this Service have more than 25% of the error budget still available.
  
  At RISK: All SLOs in this Service Have EB left, and at least one SLO for this Service has less than 25% of the error budget left.
  
  Critical: Any one SLOs in this Service has burnt through its error budget
From the header you can Delete SLO, Retire, or Edit.

If you delete an SLO any associated SLIs are deleted, as well.

If you retire an SLO, it changes the state. You can Re-activate it from the SLO page or later from the Reliability metrics tab.

Note:
If you edit an SLO, it changes the state, retires the SLO record, and opens a new copy for editing. See Create an SLO, an SLI, and Error budget policies for SRM for more information. You can reactivate the original SLO by returning to the Reliability metrics tab.
View the Overview tab and select Historic Periods from the list menu.
The periods listed are from the date the SLO was created to the present in the selected increments.
View Summary metric cards for the SLO.
The metrics show aggregate or average values depending on the type of SLIs chosen and error policy thresholds chosen. See Create an SLO, an SLI, and Error budget policies for SRM for more detailed information.
View the Service level indicators section.

This section lists your indicators by name.

View the Service level objective (SLO) history section.

Depending on your SLO type, this section displays the following in bar graph reports:

For Duration:

Error budget used
Error budget remaining
Burn rate

History graphs for the HTTP response time SLO are relatively flat.

For Count, Count by periods, or Count by occurrences:

Cumulative breach occurrences
Burn rate
Alerts, incidents & changes impacting this service

Graph showing alerts, incidents, and changes impacting this service shows a spike in the number of incidents.

Clicking into one of the analytics line chart reports shows the values on that day.

Duration is the SLO type selected when creating the SLO. It is the amount of time the service spends without breaching.


Title	Type	Description
Error budget used	Line chart	The percentage of Error budget used over the Duration. Error budget is calculated based on the provided Compliance period and Objective (percentage) when creating an SLO.
Error budget remaining	Line chart	The percentage of Error budge remaining in seconds over Duration shown. Error budget remaining: Percentage of error budget left to spend for the specified period.
Burn rate	Line chart	The Burn rate over Duration. Burn rate: Percentage rate at which an error budget is consumed.
Count, Count by periods, Count by weeks
Cumulative breach occurrences	Line chart	Number of breach occurrences.
Burn rate	Line chart	The Burn rate over Count. Burn rate: Percentage rate at which an error budget is consumed.
Alerts, incidents & changes impacting this service	Line chart	Number of alerts, incidents and changes impacting the service.

View the Details tab.
The fields in this tab are auto-populated and uneditable. See Create an SLO, an SLI, and Error budget policies for SRM for detailed information on the fields.
View the Service level indicators tab.
This tab lists the SLIs associated with this SLO.
View the Error budget policy tab.
In this tab you can add more thresholds and edit or delete existing ones.