Step 4: Create SLO

See how to create an SLO.

Tired of reading? Check out the video tutorial!

SLOs allow you to define the reliability of your products and services in terms of customer expectations. You can create SLOs for user journeys, internal services, or even infrastructure.

Configuration

With a service and its data sources configured, you can define the thresholds for Service Level Indicators. Together with a time window, these create a unique SLO.

To create an SLO in the Nobl9 UI:

1. Go to the Service Level Objectives page.
2. Click the button to start the SLO Wizard, and follow the five-step configuration process in the wizard.
3. In step 1 of the SLO Wizard:

Select Service

Select a Service from the drop-down list to tag the service this SLO applies to.






4. In step 2 of the SLO Wizard:

Select Data Source

Select a Data Source from the drop-down list.





Specify Metric

Select a type of Metric and enter a Query.

Threshold Metric

A Threshold Metric is a single time series evaluated against a threshold.





Ratio Metric

A Ratio Metric allows you to enter two time series to compare (for example, a count of good requests and total requests).

For the Ratio Metric, choose the Data Count Method:


• For the Non-incremental method, we expect it to be the components of the sum.
• For the Incremental method, we expect the value of a metric to be the current sum of some numerator.






For details on how to configure a query for each data source, refer to the in-app help panels in the Nobl9 UI or to the Nobl9 Documentation.



5. In step 3 of the SLO Wizard:

Define a Time Window

Define a Time Window: choose a Rolling or Calendar-Aligned Time Window.

Rolling

Rolling time windows are better for tracking the recent user experience of a service. The maximum limit is 31 days.





Calendar-Aligned

Calendar-aligned windows are best suited for SLOs that are intended to map to business metrics that are measured on a calendar-aligned basis, such as every calendar month or every quarter. The maximum limits are: 1 year, 12 months, 366 days.






6. In step 4 of the SLO Wizard:

Select the Error Budget Calculation Method

Select either Occurrences or Time Slices method:


• Occurences counts good attempts against the count of total attempts.
• Time Slices measures how many good minutes were achieved (minutes where a system is operating within defined boundaries) during a time window.



Add your SLO Objective(s)

You can define up to 12 objectives for an SLO:


• Enter SLO objective Display Name.
The Display Name allows you to enter a name with spaces.


• Enter unique SLO objective Name.
The Name is required and can only contain lowercase, alphanumeric characters, and dashes. For example: objective-one.


You can’t edit the SLO objective Name once you’ve created the SLO.
• Enter the Target.
Define the percentage of good events out of total events that you want to meet the target values for the SLI.


• If you selected the Time Slices method as an Error Budget Calculation Method:
• Enter the Time Slice Allowance.
Define the percentage of the time slice for which you want to meet that Target. This is used to determine if a time slice should be considered good or bad.


• Enter the target Values.
Compare the values gathered from the metric source. For example, if Values less than 200 is the objective for a Good experience, values below 200 are considered good.


• Below, you can see a query provided in step 2 of the SLO Wizard.
You can modify the query for each added objective.


7. In step 5 of the SLO Wizard:

Define SLO Attributes

• Enter SLO Display Name.
The Display Name allows you to enter a name with spaces.


• Enter SLO Name.
The Name is required and can only contain lowercase, alphanumeric characters, and dashes. For example: my-slo-name. This field is populated automatically when you enter a display name, but you can edit the result.


• Check the Create Composite SLO checkbox if you want to create a Composite SLO.
For more information on Composite SLO, refer to the Composite SLO guide.


• Select Alert Policies from the drop-down list to configure alerts.
For more information, go to the Create Alerts SLOcademy section.


• Select or add Labels.
For more information on Labels, check the Labels section.


• Attach a Link to your SLO (optional).
You can add up to 20 links to an SLO.
Enter a Display Name for the title of the link (max. 63 characters) and paste the URL.


• Enter a Description (optional).
Here you can add details such as who is responsible for the SLO (team/owner) and the purpose of creating it.




8. Click the Create SLO button.

• You can share your SLO by geting a deep link in your browser’s address bar. Just copy and share it with your teammates!

Check out the configuration video:

For this example configuration video, we will query Prometheus for a latency metric by adding the following query in the Threshold Metric box:

latency_west_c7{code="ALL",instance="localhost:3000",job="prometheus",service="globalcount"}

In this example, we’ll set the target at 99%. This means 99% of occurrences for latency will be with the tolerance defined below. We set the desired value to less than 2000.

This means that for 99% of the events in the time window, we would expect the latency to be under 2 seconds to meet our objective. Any event with a latency over 2 seconds causes error budget to burn. If more than 1% of the events during the time period have a latency over 2 seconds, we will run out of error budget.

Video 1: Creating an SLO

• It takes a few minutes for the data to be populated. Remember: if you selected a longer time window, it may take longer for the chart to appear as the data is downsampled into larger slices for the chart view.

note

Check out also the video on adding Prometheus data source using the Agent connection method in Nobl9 UI.

Bravo! You've just created the SLO! Now, proceed to the next section to learn how to manage and monitor your SLOs.