Observability and tracing · Lesson 12 of 15 · 5 min

Calculate error-budget posture

Error-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.

Open the lab Course map

Mastery 0/3Run itExplain itApply it

learner@clairos:~ $

↑ history · Tab complete · Ctrl+C cancel · Esc, Tab to leaveExit 0

Your objectives

Hints are always available. Wrong turns never cost XP.

1
Read the case evidence
Read /opt/ai-lab/cases/aiops-observability-tracing-012.json. Separate the recorded facts from your assumptions.
Hint & worked example
Error-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.
The complete case JSON is read successfully.
```
cat /opt/ai-lab/cases/aiops-observability-tracing-012.json
```
Common mistake to avoid: A 99 percent target allows any failure count below 1000.
2
Isolate the deciding signal
Select the observed_failures field from the case JSON. What does it establish—and what does it not establish?
Hint & worked example
Treat this request-based budget as exceeded by 20 failures and review risky changes.
A successful JSON query isolates observed_failures.
```
jq .observed_failures /opt/ai-lab/cases/aiops-observability-tracing-012.json
```
Common mistake to avoid: Using a different case or an unrelated signal as the justification.
3
Record your operational decision
Choose the justified code: pause-risky-change, change-without-evidence, or ignore-the-signal. Save that one code followed by a newline in /home/learner/lab/aiops-observability-tracing-012-decision.txt.
Hint & worked example
Treat this request-based budget as exceeded by 20 failures and review risky changes.
The decision artifact contains the correct code, not just a matching command in history.
```
printf '%s\n' 'pause-risky-change' > /home/learner/lab/aiops-observability-tracing-012-decision.txt
```
Common mistake to avoid: A 99 percent target allows any failure count below 1000.

Understand the pattern

Error-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.

Interpret the evidence

Treat this request-based budget as exceeded by 20 failures and review risky changes.

A tempting mistake

A 99 percent target allows any failure count below 1000.

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-012.json

{
  "fixture": "Fictional training data; not a live measurement.",
  "eligible_requests": 10000,
  "success_target": 0.99,
  "allowed_failures": 100,
  "observed_failures": 120
}

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

$ jq .observed_failures /opt/ai-lab/cases/aiops-observability-tracing-012.json

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

$ printf '%s\n' 'pause-risky-change' > /home/learner/lab/aiops-observability-tracing-012-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 “pause-risky-change” to stop being the justified action. Do not silently replace missing evidence with a guess.

Explain it

What does the evidence in “Calculate error-budget posture” justify?Treat this request-based budget as exceeded by 20 failures and review risky changes.A 99 percent target allows any failure count below 1000.Make the change now and gather the missing evidence afterward.

Apply it elsewhere

A colleague concludes: “A 99 percent target allows any failure count below 1000.” What should you do?Accept it because the training command completed.Treat this fixture as a live measurement.Reject that conclusion; return to the case evidence and its stated limits.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Build an incident timeline Try 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

Case methodology: evidence, limits, decision