Error Budget Burndown: Your Service's Reliability Fuel Gauge
An error budget burndown chart is a fuel gauge for your service's reliability. It shows how much 'allowable downtime' you've used, helping you decide when to ship features versus fix bugs. The footgun is ignoring a steep burn rate until it's too late.
Why it exists
Teams need a quantitative way to balance feature velocity with stability. Without a shared framework, decisions about whether to ship a new feature or fix a reliability issue are based on gut feelings, leading to either fragile systems or stagnant products. Error budgets provide this data-driven language.
The mental model
An error budget burndown chart is a visual representation of your risk tolerance over time. Your Service Level Objective (SLO), like 99.9% availability, defines your reliability promise. The inverse, 0.1%, is your "error budget"—the amount of unreliability your users can tolerate. The burndown chart shows how much of this budget you've consumed. A steep downward slope means you're burning budget quickly and risk breaking your promise. A slow decline means you're operating reliably.
How it works
First, you define an SLO over a rolling window (e.g., 30 days). For a 99.9% availability SLO, your error budget is 0.1% of that time, roughly 43 minutes. The system tracks "bad events" (like 5xx errors) against total events. The burndown chart plots the remaining budget, starting at 100% and decreasing with every error. An "ideal" linear burn rate is often plotted for comparison. If your actual burn rate is faster than the ideal, you're on track to breach your SLO.
When to use it
Use a burndown chart to guide engineering priorities. If you have over 50% of your budget left halfway through the month, it's a green light to ship features. If you've burned 75% of your budget in the first week, it's a clear signal to freeze risky deployments and prioritize reliability work. It makes the abstract goal of "being reliable" a concrete, manageable resource.
When not to use it
The chart is less useful for services with no clear user-facing impact or for internal tools where high reliability isn't the primary goal. It's also less effective for very short time windows (e.g., one hour) where a single outage consumes the entire budget, offering little predictive value. Its power lies in visualizing trends over weeks or months.
One canonical example
A platform team has a 99.9% availability SLO over 30 days for a key service. After a bad deployment, their burndown chart shows a sharp vertical drop, consuming 50% of their monthly budget in one hour. The team immediately rolls back the change and freezes new deployments to stabilize the system. The chart provided the objective data needed to justify halting feature work to prevent a full SLO breach.
Interview question
Which scenario, based on an error budget burndown chart, would most clearly signal that an engineering team should prioritize shipping new features?
- a.The actual error budget burn rate is significantly slower than the ideal linear burn rate.
- b.More than half of the error budget remains available halfway through the monitoring window.Correct
- c.The chart indicates a steep downward slope, consuming budget rapidly.
- d.The team has already breached their Service Level Objective (SLO) for the current period.
Why? this is the answer
The card explicitly states, "If you have over 50% of your budget left halfway through the month, it's a green light to ship features." While a slower burn rate (option A) is a positive sign, the card provides the remaining budget condition as the direct trigger for prioritizing new features.
Just read this? Test yourself on what you have been reading.
Read the original → oneuptime.com
You just looked this up. Could you explain it out loud?
That is the part interviews actually test. Tezvyn takes questions like this one and gives you what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on sre — each one lists the topics its interview covers.
See open roles