Course contentsShow
← System Design
Lesson 1279 of 1,91932. Monitoring and AlertingFree lesson

Error Budgets: The Core Concept

Define error budgets as the allowed amount of unreliability (100% - SLO) that permits innovation and change.

Error Budgets: The Core Concept

What you'll learn: How error budgets quantify the allowed unreliability that enables safe innovation.

The Core Idea

An error budget is the mathematical inverse of your SLO — it represents the amount of "failure" you can afford before breaking your reliability promise.

If your SLO is 99.9% availability, your error budget is 0.1% downtime (100% - 99.9%). This isn't a shameful failure allowance — it's a resource you can deliberately spend.

Why Error Budgets Matter

Think of an error budget like a financial budget. If you promise customers 99.9% uptime, you're essentially saying "we can be down for 43 minutes per month." That 43 minutes is your budget to spend on:

  • Deploying new features (which might occasionally fail)
  • Infrastructure changes (migrations, upgrades)
  • Experimentation (testing new technologies)
  • Planned maintenance

Without an error budget, teams become paralyzed — too afraid to deploy or innovate because any failure feels catastrophic. With a budget, teams have a shared, objective metric for balancing innovation against stability.

How It Works in Practice

  • Budget remaining: Deploy freely, take calculated risks
  • Budget depleted: Freeze risky changes, focus on reliability improvements
  • Budget consistently underused: Your SLO might be too conservative; consider tightening it or investing saved engineering effort elsewhere

This creates a natural feedback loop: reliability issues automatically trigger stability work, while excellent reliability permits faster innovation.

Key Takeaway: Error budgets transform reliability from a binary pass/fail into a managed resource — they're the allowed unreliability (100% - SLO) that lets teams innovate safely while maintaining customer trust.