Composite SLOs Guide

Reading time: 0 minute(s) (0 words)

Nobl9 has introduced Composite SLOs, a concept that allows aggregating multiple SLO objectives within a single SLO to represent an overall reliability performance view of your service. SLOs can now capture an end-to-end user journey for a complex service.

tip

Check the Use Cases of Composite SLOs to see how Composite SLOs can be used in real-life scenarios.

Composite SLOs - Rules at a Glance

Like all other resources in Nobl9, Composite SLOs are grouped under Projects and Services:

• Each SLO you define can only be part of one Composite SLO.
• You can combine a set of objectives within a single SLO into a Composite SLO.
  • You can define up to 12 objectives for an SLO.
  • You can modify the query for each objective.

Some definitions

Composite SLO is a combination of multiple error budgets in a single SLO into one error budget that burns the budget if any of the component objectives are burning.

Composite SLO creates a new error budget calculation called "composite.” For the composite error budget burn, each objective contributes equally to this composite error budget.

The composite error budget is calculated minute by minute. In each minute, if any component objectives have a burn rate over the threshold you set, the minute is considered a bad minute for the composite.

Composite SLOs and Annotations

You can add an annotation to a Composite SLO. The added annotation appears in all the charts for the Composite SLO and the objectives.

note

For more information on annotations, refer to the SLO Annotations | Nobl9 Documentation.

Composite SLOs and Error Budget Calculations

Composite SLOs have a new error budget calculation method called the Composite Error Budget. It aggregates the error budgets of all the objectives in the SLO. Here's a glance at some rules that underlie changes in the calculation methods:

• The Composite Error Budget burns if the error budget for any of the SLO objectives within the Composite SLO is burning.
  • For a Time Slice SLO, this is binary, depending on whether it was a good or bad minute. If it was a bad minute for any individual objective, it’s considered a bad minute for the Composite SLO.
  • For an Occurrences SLO, the Composite Error Budget is calculated based on the error budget burn rate, which measures how fast the error budget is consumed following the greater than condition. The default burn rate value is 1x and can be customized.

tip

The target of a Composite SLO and its Objectives can be different, as such:

• A single bad point for the Objective can burn the whole Composite SLO’s error budget.
• A very high error budget burn of the SLO Objective is treated the same as any other burn if it matches the Composite SLO burn rate condition.
  

Image 1: Composite SLO and Error Budget Calculations

Let’s put these assumptions into an example:

Composite SLO has the Error Budget Burn value set as 2x. Consider the following:

• scenario A: SLO Objective’s Error Budget Burn value = 2x
• scenario B: SLO Objective’s Error Budget Burn value = 20x
  

A and B scenarios result in the same Composite SLO calculations. SLO Objective’s Error Budget Burn values don't affect the Composite SLO calculations. In this case, both Objectives burn the same amount of reliability but can exhaust Composite SLO’s error budget sooner.

For more details, check the section below

Tips for Configuring Composite SLOs

Occurrences Method

• Setting a high target for the standard objective will cause its burn rate to spike more into high values. The maximum burn rate value is an inverse of the budget.

  • For example, a budget of 10% (target: 90%) will have a maximum burn rate of 10x (1/0.1), while a budget of 3% (target: 97%) will have a maximum burn rate of 33.33x (1/0.03). This is true for both standard and composite objectives.

• By manipulating standard objective targets and the composite’s burn rate threshold, you can choose how sensitive the composite is to the burning of its aggregated objective’s budget:

  Composite’s burn rate condition threshold	Standard objective target	How fast composite’s budget is burning
  Low	High	Very sensitive
  High	High	Sensitive
  Low	Low	Insensitive
  High	Low	Very Insensitive

Timeslices Method

• The Target of standard objectives doesn’t affect _the _composite’s__ error budget.
  Calculations are based on whether individual minutes of standard objectives are good or bad, regardless of how much a bad minute would burn its objective’s budget.

  • Each bad minute of both composite or standard objective will lower reliability burn down by the same amount that is equal to:

    
    • For example, each bad minute in one week rolling SLO will lower reliability burn down by around 0.01% = 1/(7*24*60).

  • Note that the budget target doesn’t affect how fast reliability burn-down drops.
    In the case of timeslices, it matters how many maximum minutes (number of minutes in time window) we allow to be bad. Following the previous example, a 90% target gives 1008 minutes in the budget 7*24*60*(1-90%), so 1 bad minute will burn around 0,1% of the budget.

• The time window's length significantly affects how fast a budget will burn for both Composite and standard objectives.

Observations on Composite Budgets

Composite budgets will usually burn faster than individual aggregated standard objective budgets.

That is because a composite budget is burnt when any aggregated budgets are burnt fast enough (occurrences) or have a bad minute (timeslices); it will be burnt more often than any of its individual objectives.

The more standard objectives Composite aggregates, the higher the chance that at least one will burn the budget fast enough (occurrences) or have a bad minute (timeslices).

This means that Composites with more aggregated objectives will usually burn their budget faster than those with fewer.

tip

Composite will usually burn at least as fast as its fastest-burning aggregated objective.

To get a more actionable Composite SLO, set more relaxed parameters (i.e., budget target, threshold value, time slice target) on aggregated objectives than you usually would if they were individual SLOs.

SLO is actionable if it can warn you about the potential exhaustion of the error budget early enough so you can do something about it before it happens. A Composite SLO that exhausts its budget as soon as any of its constituent budgets are burnt isn't actionable.

Reliability Burn Down

Composite’s reliability burn down is not an average of reliability burn downs of its aggregated objectives.

This means that any intuitions you might have regarding an average will likely not be true regarding the Composite.

tip

The Composite’s reliability burndown can be higher or lower than any or all aggregated objectives.

Composite’s budget calculations require information from all its aggregated objectives.

• If data for any aggregated objective query is missing or delayed, then the composite’s budget calculation will also be missing or delayed.

• Composite’s reliability burn down chart data resolution will be equal to or lower than aggregated objective with the lowest data resolution.

  tip

  Composing objectives with dense and sparse SLI metrics will give a budget that behaves as one calculated from sparse metrics.

Uniqueness of Threshold Values

To enable uniqueness in error budget calculations in Composite SLOs, Nobl9 uses the threshold value to identify specific objectives. You must set a unique target value across all objectives within one Composite SLO**.

If you want to use similar threshold values for different objectives in your Composite SLO, we recommend differentiating them by setting varying decimal points for each objective. For example, if you want to use threshold value 1 for two objectives, set it to 1.0000001 for the first objective and to 1.0000002 for the second one, as in the example below:

- apiVersion: n9/v1alpha
  kind: SLO
  metadata:
    name: my-composite-slo
    project: my-composite-slo
    ...
    objectives:
    - countMetrics:
      ...
      name: objective-1
      target: 0.95
      value: 1.0000001
    - countMetrics:
      ...
      name: objective-2
      target: 0.91
      value: 1.0000002

Defining Composite SLOs

You can define your Composite SLOs through the Nobl9 UI or by applying a YAML file through sloctl.

Creating Composite SLOs in the UI

To create a Composite SLO in the Nobl9 UI:

1. Navigate to Service Level Objectives.
2. Click the button.
3. In step 1 of the SLO wizard, select the Service the SLO will be associated with.
4. In step 2, select a Data Source for your SLO.
5. Select the type of Metric. The available types vary depending upon the data source used. Check the Getting Started Guide for more details.
6. Enter a Query for the metric you selected.
7. In step 3, define a Time Window for the SLO.
8. In step 4, specify the Error Budget Calculation Method and your Objective(s). You can define up to 12 objectives for an SLO:

• For the Occurrences method:

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

  • Enter a 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.

    note

    During the SLO objective unique identifier grace period, you can update the name for existing SLOs only through sloctl, and you can only do that once. Refer here for more information.

  • Enter the Target (mandatory).
    Define the percentage of good events out of the total events you want to meet the target values for the SLI.

  • Enter the target Values (mandatory).
    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.

  • You can modify the query for each added objective.

• For the Time Slices method:

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

  • Enter a 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.

    note

    During the SLO objective unique identifier grace period, you can update the name for existing SLOs only through sloctl, and you can only do that once. Refer here for more information.

  • Enter the Target (mandatory).
    Define the percentage of good events out of the total events you want to meet the target values for the SLI.

  • Enter the Time Slice Allowance (mandatory).
    Define the percentage of the time slice you want to meet that Target. The Allowance determines whether a time slice should be considered good or bad.

  • Enter the target Values (mandatory).
    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.

  • You can modify the query for each added objective.

For details on further steps, refer to the Getting Started Guide.

Creating Composite SLOs in sloctl

Refer to the YAML Guide | Nobl9 Documentation to see how you can define a Composite SLO in a YAML file.

Editing Composite SLOs

You can edit a Composite SLO by clicking the Edit button next to the Composite SLO in the Grid View.

• In step 4 of the SLO wizard, you can edit:

  • The Target for both the Occurrences and Time Slices error budget calculation methods
  • The Time Slice Allowance for the Time Slices error budget calculation method
  • The Values for both the Occurrences and Time Slices error budget calculation methods
  • The Query for each added Objective by clicking View Query and modifying it

• You can also add a new Objective to the Composite SLO. Once you’ve saved your changes, error budget calculations proceed with this objective included. Similarly, you can remove a defined Objective. Error budget calculations proceed without this objective after you’ve saved your changes. Calculations do not get reset.

• In step 5 of the SLO wizard, you can uncheck the Create Composite SLO checkbox. When you save your changes, all the previously added objectives become individual, regular SLOs (the Composite SLO no longer appears in the Nobl9 UI and no history is preserved). Similarly, you can edit a regular SLO and check the Create Composite SLO checkbox in this wizard step. When you save your changes, the SLO becomes a Composite SLO.

note

The changes you make to the Composite SLO are reflected within a few minutes. The Composite SLO then starts to show an updated burndown.

Viewing Composite SLOs in Grid View

Like standard SLOs, you can view your Composite SLOs in the Grid View in the Nobl9 UI. Here, you can see the Composite SLO’s Reliability Burn Down chart, remaining error budget, and such.
You can quickly identify them by their special icon and blue header:

Image 2: Composite SLO in Grid View

To open the Composite SLO's details view, click the name of the Composite SLO.

You can inspect the Reliability Burn Down and Error Budget Burn Rate charts in the Composite tab.

Image 3: Composite SLO details view

In the Objectives tab, you can see a list of all underlying Objectives with their data (the SLI chart and Reliability Burn Down chart). This lets you see how each contributes to burning the Composite SLO’s error budget.

Image 4: Composite SLO Objectives tab

Composite SLOs and Data Export

With the rollout of Composite SLOs, we've added a new column (composite) at the end of each CSV row. The new column indicates whether the row in the CSV file contains composite SLOs-related data.

When the value for the composite column is true, you can find the data for your composite SLOs in the following columns in the CSV file:

Column name	Data type	Description
budget_target	DOUBLE	Objective’s target value (percentage in its decimal form) or composite’s target value.
objective_value	DOUBLE	Objective value or composite SLO’s burn rate condition value.
objective_operator	STRING	An operator used with raw metrics or composite’s burn rate condition operator. One of the following values: lte - less than or equal lt - less than get - greater than equal gt - greater than
composite	BOOLEAN	Indicates whether the row contains composite-related data (true means a row contains composite data).

Useful Links

Composite SLO - Troubleshooting

Composite SLOs | Nobl9 Terraform Documentation

Replay and Composite SLOs