📟Error Budget
Also known as Reliability Budget, Error Budget Policy
The amount of failure a target allows. Spend it on change, or stop when it is gone.
Think of it like
It is like pocket money for mistakes. You can spend it, but when it is gone, you stop.
Example
An SLO of 99.9% over 30 days allows about 43 minutes of failure. A bad release burns 30 of them, so the team pauses big launches until the month resets.
Why it matters
It ends the fight between shipping fast and staying stable. The number decides, not the loudest voice.
Definition
Common mistake
Key takeaways
- 1100% minus the SLO. The gap is the budget.
- 2Spend it on change. Releases and tests use it up.
- 3Empty means stop. No budget left, no risky releases.