Paths/DevOps Engineer/Observability / SLOs & Error Budgets
Write the SLO and Its Error Budget
The product team promised customers 99.9% availability this quarter — a promise nobody can act on until it is written down as two numbers. Record the target in ~/slo/slo.txt and work out the error budget it implies into ~/slo/budget.txt.
Validator
IDLE — checks run live as you type commands; submit when done
01Requirements
live checks- Directory ~/slo exists containing slo.txt and budget.txt○
- slo.txt records the availability target of 99.9○
- budget.txt records the matching error budget of 0.1○
02Walkthrough
1 of 6 revealed- 01
Make a home for the SLO
Service-level work tends to accrete files — targets, budgets, burn-rate notes. One directory keeps them together.
mkdir ~/slo - 5 locked · each failed submit reveals one
03Stuck?
0 of 3 revealedTake a hint without losing the lab — each one points at the thing to look at, not at the answer.
04AI Tutor
guides, never solvesTell me what you're stuck on — I'll nudge, not solve. Which requirement are you looking at?
04Notebook
saved locally in this browserlearner@lab — ubuntu:24.04
Session is disposable
↑/↓ recalls commands · Ctrl+Enter submits · type help for the command list