Browsing as a guest. Sign in to save your progress and earn XP as you complete chapters.
SLIs, SLOs & Error Budgets
5 min read
You'll learn to
- -Compute an error budget from an SLO
SLI, SLO, SLA
- -SLI (Service Level Indicator): the actual measured number, e.g. "99.87% of requests succeeded last month."
- -SLO (Service Level Objective): the internal target you're designing and operating toward, e.g. "99.9% success rate."
- -SLA (Service Level Agreement): an external, often contractual promise with real consequences (refunds, penalties) if missed.
Error Budgets
If your SLO is 99.9% uptime, you have an explicit budget of about 43.8 minutes of allowed downtime per month. Instead of treating every second of downtime as an unplanned failure, teams spend that budget deliberately (on risky deployments, on experiments, on maintenance windows) and only slow down shipping once the budget for the month is exhausted.
This reframes reliability as a resource you allocate, not an absolute you chase. 100% uptime isn't just unrealistic: deliberately pursuing it means you'd never be able to ship anything new.
Interview Signal is part of Pro
See a real weak answer next to a real strong one for this exact topic.
Quiz is part of Pro
Test what you just read with a short quiz, and bank the XP.