Skip to content
BENIBIX Learn

Error Budget

Infrastructure📟 ReliabilityService Levels

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

An error budget is how much failure an SLO allows. It is 100% minus the target. An SLO of 99.9% leaves 0.1% of requests free to fail. While budget is left, the team can ship new features and take risks. When it is used up, new releases wait and the team works on reliability.
The shaded gap is the error budget left. Every failure eats into it.

Common mistake

Treating any spent budget as a failure. It is meant to be spent on change, as long as it is not overspent.

Key takeaways

  1. 1
    100% minus the SLO. The gap is the budget.
  2. 2
    Spend it on change. Releases and tests use it up.
  3. 3
    Empty means stop. No budget left, no risky releases.