SLO Details

The SLO Details page displays the configuration and current performance of an SLO.

Details

Each SLO lists its configuration at the top of the page. Depending on the SLO type, this section may include Type, Objective, Time Window, Service, Latency Threshold, Contact Points, Labels, Matchers, and SLI Query.

The main performance indicators of an SLO are:

Status

The current state of the SLO based on good and bad events compared to the objective. Displayed in green when meeting the objective and red when below it.

Objective

The target percentage of good events over the configured time window. For example, a 99.9% objective means no more than 0.1% of events can be bad.

Error Budget Remaining

The remaining budget of allowable bad events based on the objective. For example, with a 99.9% objective and 10,000 total events in a 7 or 30 day window, the error budget allows only 10 bad events (0.1% of 10,000).

Graphs

All SLO types include four graphs:

Error Budget Remaining

Shows how much error budget remains over time. This graph has two modes:

Fixed Window

Shows the budget burndown over the configured time window (7 or 30 days), starting at 100%. The budget can only decrease within this view. Use this for a quick snapshot of recent budget consumption.

fixed error remaining

Rolling Window

Calculates budget remaining at each point using the full 7 or 30 day lookback. Unlike fixed, the budget can move both up and down — as older errors age out of the lookback window, available budget increases. Use this to see whether your budget is recovering or continuing to decline.

rolling error remaining

In this example, we can see the budget is recovering slightly over time.

Burn Rate

Shows how fast you are consuming your error budget. The burn rate is a multiplier — a rate of 1 means you will exhaust the budget exactly by the end of your time window.

burn rate
  • 1 — entire budget consumed in 7 days (or 30 days)

  • 2 — budget consumed in half the time (3.5 or 15 days)

  • 10 — budget consumed in roughly 17 hours (or 3 days)

  • 0.5 — only half the budget consumed over the full window

Above 1 means budget is burning unsustainably fast. Below 1 means you are on track to have budget remaining.

Good Events

Count of good events (successful requests) over time.

Bad Events

Count of bad events (failed or slow requests) over time.

Types

Availability and Latency SLOs

Availability and Latency SLOs each measure a single metric, so the details page shows performance for that metric directly.

Current values for Status, Objective, and Error Budget Remaining are displayed near the top of the page.

slo details

Metric and Custom SLOs

Status by Group

For Metric and Custom SLOs, the current Status, Objective, and Error Budget Remaining values are displayed at the bottom of the page in a table grouped by your metric’s aggregation.

If your metric has no aggregation, a single Overall row is shown. If your metric includes a group by, each group is shown as its own row with individual status, and error budget values.

For example, when looking at an HTTP request metric, you can group by path and see the status for each path individually.

metric custom group by status

Graphs by Group

Grouping also affects the graphs above — each graph separates data by group.

metric good aggregation

To see all groups, click the +29 indicator at the bottom right of the group list to expand it.

metric good aggregation expanded

To filter the SLO to a specific group, click on its name.

metric good aggregation selected