error budget
The amount of failure an SLO allows over its window: one minus the target, for example 0.1 per cent of requests at 99.9 per cent.
In more detail
The budget can be spent deliberately on releases, migrations and experiments. When it is exhausted, reliability work takes priority. Burn rate measures how fast it is being used.
Examples
error budget 2,000 failed requestsA canary step passes while its error rate stays within the budget.1,000,000 requests at a 99.9 per cent objective allows 1,000 failures.In this course: Recording errors against the budget during a load test shows whether a system can meet its objective under realistic traffic. When the budget is spent, teams usually slow down risky changes until reliability recovers.Related terms
- service level objective — A target for a service level indicator over a time window, such as 99.9 per cent of checkouts succeeding over 30 days.
- burn rate — How fast the error budget is being spent, compared with spending it exactly evenly over the SLO window.
- error budget policy — An agreed rule for what a team does when its error budget is burning or spent, such as pausing risky releases.
- canary release — Sending a small share of real traffic to a new version first, and increasing it only while its metrics stay healthy.
- error rate — The share of requests that fail, reported alongside latency so a fast result is not mistaken for a healthy one.
Taught in
- Service Level Objectives — DevOps & Site Reliability Engineering
- Error Budgets — DevOps & Site Reliability Engineering
- Observability Context — DevOps & Site Reliability Engineering
- Continuous Delivery: Blue-Green & Canary Pipelines — Production Full-Stack Engineering
- Observability Versus Monitoring — Full-Stack Observability: Metrics, Tracing & Logging
- Why A Histogram Beats An Average — Full-Stack Observability: Metrics, Tracing & Logging
- Service Level Indicators — Full-Stack Observability: Metrics, Tracing & Logging
- Service Level Objectives — Full-Stack Observability: Metrics, Tracing & Logging
- Error Budgets And Burn Rate Alerts — Full-Stack Observability: Metrics, Tracing & Logging
- Forty Seconds At Two: Push, Pull And Service Discovery — Prometheus Certified Associate (PCA) Exam Prep
- Ninety Nine Percent Of What? SLIs, SLOs And SLAs — Prometheus Certified Associate (PCA) Exam Prep
- Observability Sprint: One Failed Checkout — Prometheus Certified Associate (PCA) Exam Prep
- Seventy Seven Percent, Book Now? The Full Mock — Prometheus Certified Associate (PCA) Exam Prep
- Observability As A Design Input — Scalable System Design & Distributed Architecture
- Load Testing: Percentiles Over Means — Automated Testing, TDD & Quality Engineering
References
- Google SRE book: Embracing Risk
- Google SRE workbook: Error Budget Policy
- Google SRE book: service level objectives