Don't Panic — Error Budgets

An error budget is the portion of an SLO that permits imperfect service. It is not an allowance for careless outages. It is a way to stop reliability and feature delivery arguing by instinct when a number can carry the argument instead. The spreadsheet has brought a ruler to the emergency. This is unusually helpful.

Everything hangs from the service level indicator, or SLI: a measure of a user journey. For a request service, that can be good requests divided by eligible requests. The word “eligible” is doing more work than it appears to be doing. It decides which requests count, which do not, and whether the resulting number describes users or merely describes a convenient data source.

The service level objective, or SLO, states the target for that indicator over a window. The budget is the complement. A 99.9 percent target leaves 0.1 percent for bad events. This does not mean a service must use the allowance, like a holiday nobody wanted but HR insisted existed. It means that a release decision has a shared boundary when failures occur.

The next useful figure is burn rate, the speed at which current errors consume that allowance. Remaining budget says how much room is left. Burn rate says whether the room is disappearing at a pace that deserves a page, a ticket, or a careful look at the dashboard before somebody presses a deploy button with great confidence and poor timing.

The surprising part is that the arithmetic is the least troublesome piece. A precise budget can still be wrong if the SLI misses the journey users care about, if a global total hides one damaged region, or if a low-traffic service turns one failed request into a dramatic short-window rate. The number needs its window, population, data source, and segmentation attached. Without those, it is a percentage wearing a tie.

An error budget policy is what makes the measurement consequential. It names the actions near exhaustion, the exceptions for urgent security or reliability work, the people who can decide, and the route for disagreement. Without it, the budget can measure trouble very accurately while nobody has authority to change the plan.

Read the Intro for the full control loop and the choices behind an SLI and SLO. Use the Slides when the relationship between window, budget, burn rate, and policy needs to fit in one glance. Keep the Cheatsheet nearby for the formulas and diagnostic signals. The Quiz checks the distinctions that tend to tangle. The practice exercise then turns a fictional API’s measurements into a release decision, which is where this idea stops being a decorative decimal.

Don't Panic — Error Budgets

Relevant careers