Say it like this
- We have burned through our error budget for this quarter.
- We need to preserve our error budget before the holiday weekend.
- The error budget allows us to ship features faster this month.
Use it at work
Making decisions
- We've used 80% of our error budget, so let's slow down releases.
- We still have error budget, so we can ship.
After an incident
- That outage burned most of this month's error budget.
- Let's freeze features until the error budget recovers.
Planning
- Our SLO is 99.9%, so the error budget is 43 minutes a month.
- Who decides what happens when we run out of error budget?
Don't say this
Error budget is not about feature prioritization; it is about acceptable system failures. You spend error budget when incidents occur, not when deploying features.
Don't mix it up
| Term | What it is | Who writes or uses it | When |
|---|---|---|---|
| error budget | Allowed failure under an SLO | SRE, engineering | Release decisions |
| SLO | Internal reliability target | SRE | Monitoring |
| SLA | Promise to customers, with penalties | Sales, legal | Contracts |
Practice
Try it
4 quick exercises
1. Your service had an incident that caused 10 minutes of downtime. How would you describe its impact?
2. With a 99.9% SLO, we have approximately 43 minutes of _______ per month.
3. Which sentence uses 'error budget' incorrectly?
4. Rewrite using error budget: 'We promised users the system would be up 99.95% of the time, so we can only have about 22 minutes of downtime per month.'
Say it out loud
Phrase 1 of 3
"We have burned through our error budget for this quarter."
We don't save your recording. The word check uses your browser's speech recognition.
More about error budget
Real examples(3)
- in a standup
"We're still within our error budget for the month, so we can proceed with the database migration next week."
- in a code review
"Given that we have used 60% of our error budget already, we should make sure this change is well-tested before merging."
- in a team meeting
"Our SLO is 99.95% uptime, which gives us roughly 22 minutes of error budget per month."
More mistakes(2)
Handle with care. Often confused with bug tolerance or QA acceptance criteria. Error budget is specifically about planned downtime or failures measured against reliability targets (SLO), not just acceptance of any bugs.
- ✕Our error budget is zero because we have no bugs in production.✓Our error budget is the 0.1% downtime we can tolerate; bugs don't directly consume it unless they cause outages.
Error budget relates to actual service unavailability or failures, not the absence of bugs. A bug that does not affect uptime does not consume the error budget.
- ✕We increased our error budget by fixing code quality issues.✓We can use more of our error budget this month because we reduced the incident rate through code quality improvements.
You do not increase error budget; you reduce the rate at which incidents consume it. The budget itself is determined by your SLO.
Other forms(2)
- error budget noun
"The error budget is calculated based on the agreed SLO with customers."
- error budgets (plural) noun
"Different services may have different error budgets depending on their criticality."
Often used with(5)
- consume error budget · To use up part of the allowed downtime (usually by an incident or failure)
- remaining error budget · The amount of downtime or failures still available before the SLO is violated
- burn error budget · To rapidly use up the available error budget through multiple incidents
- error budget exhaustion · When the error budget is completely used and the SLO is at risk
- within error budget · Still meeting the SLO; not yet having consumed all available failures
Similar words(3)
- failure budget · Nearly identical term; sometimes used interchangeably, though error budget is more common in SRE contexts
- downtime allowance · More general term; less specific than error budget which ties directly to SLOs
- reliability buffer · Similar concept but less precise; does not quantify the exact percentage like error budget does
Opposites(3)
- SLO breach
- outage
- system failure
Questions(5)
- What does error budget mean in software engineering?
- Error budget is the maximum amount of downtime or failures a service can experience while still meeting its Service Level Objective (SLO). For example, if your SLO is 99.9% uptime, your error budget is 0.1% downtime per month, which equals roughly 43 minutes. It represents a quantified tolerance for system failures.
- How do you use error budget in a sentence at work?
- You might say: 'We have consumed 30% of our monthly error budget due to the database incident' or 'Since we still have error budget remaining, we can proceed with the planned deployment.' Error budget is used when discussing incident impact, deployment decisions, and reliability planning.
- Is error budget formal or informal?
- Error budget is a formal technical term used in professional software engineering and SRE contexts. It appears in formal documents like SLOs, incident reports, and engineering strategies, though it is also used in casual team discussions and standups.
- How is error budget calculated?
- Error budget is calculated by subtracting your SLO from 100%. For example: 100% - 99.9% = 0.1% error budget. For a month, you multiply this by the total minutes in a month (approximately 43,200), so 0.1% × 43,200 = 43 minutes of acceptable downtime.
- What happens when error budget is exhausted?
- When error budget is exhausted, your service is in breach of its SLO. This typically triggers actions such as halting new feature deployments, focusing on stability and incident prevention, and potentially triggering SLA penalties if customers are affected.
