Skip to content
Clairos Learn

Observability and tracing · Lesson 11 of 15 · 9 min

Read an SLO window

An SLO defines a target and window for a user-visible measure. Read the denominator and exclusions before comparing current behavior to the target.

Open the labCourse map
Mastery 0/3Run itExplain itApply it
learner@clairosSimulated AI Ops lab
learner@clairos:~ $
↑ history · Tab complete · Ctrl+C cancel · Esc, Tab to leaveExit 0

Understand the pattern

An SLO defines a target and window for a user-visible measure. Read the denominator and exclusions before comparing current behavior to the target.

Interpret the evidence

Record 80 failures against a 100-failure allowance in this simplified request-count SLO.

A tempting mistake

The target allows zero failures under every possible window.

All names, measurements, prices, versions, and thresholds in this exercise are fictional training data. The evidence supports this bounded scenario, not a claim about a live provider.

Worked example and expected result
$ cat /opt/ai-lab/cases/aiops-observability-tracing-011.json
{
  "fixture": "Fictional training data; not a live measurement.",
  "target_success": 0.999,
  "window": "30 days",
  "eligible_requests": 100000,
  "failures": 80
}

Exit status: 0. The command completed successfully in the training fixture.

$ jq .failures /opt/ai-lab/cases/aiops-observability-tracing-011.json
80

Exit status: 0. The command completed successfully in the training fixture.

$ printf '%s\n' 'record-budget-remaining' > /home/learner/lab/aiops-observability-tracing-011-decision.txt
(no output; exit 0)

Exit status: 0. The command completed successfully in the training fixture.

Try a variation

Name the assumption that would have to change for “record-budget-remaining” to stop being the justified action. Do not silently replace missing evidence with a guess.

Explain it

What does the evidence in “Read an SLO window” justify?

Apply it elsewhere

A colleague concludes: “The target allows zero failures under every possible window.” What should you do?

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Calculate error-budget postureTry an incident drill

Anonymous lesson and mastery progress lasts for this session. Sign in to keep synced lesson XP between sessions; mastery stays device-local. No speed bonus, lost lives, or hint penalties.

Keep learning

  1. 01Review model saturationSaturation combines utilization, queueing and service time. High utilization without queue growth can mean useful work; a growing queue gives the observation operational context.Practice
  2. 02Calculate error-budget postureError-budget posture compares observed bad events with the allowance implied by the SLO. Record the window and avoid mixing request-based and time-based budgets.Practice
  3. 03Build an incident timelineAn incident timeline preserves ordering, versions and the distinction between observations and interventions. Use timestamps with a shared timezone or offset.Practice

Case methodology: evidence, limits, decision