Q: Your team is adopting SRE practices. The VP asks you to define an "Error Budget" for a critical API. What is it, and how does it influence engineering decisions?
An Error Budget is the maximum amount of unreliability permitted over a time window, derived directly from the SLO (Service Level Objective).
Want to master this scenario in a live sandbox? The Linux Foundation's Certified System Administrator (LFCS) & SRE Track covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "During an on-call shift, our alerts triggered when a critical Linux production server exhibited this behavior. The interviewer is testing: SRE fundamentals, error budgets, SLO-driven development.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
An Error Budget is the maximum amount of unreliability permitted over a time window, derived directly from the SLO (Service Level Objective).
- Error Budget = 100% – 99.9% = 0.1%
- In minutes: 30 × 24 × 60 × 0.001 = 43.2 minutes of allowed downtime per month
- Budget remaining (healthy): Engineering can deploy aggressively, run experiments, ship new features. The system can tolerate some failures.
- Budget exhausted (unhealthy): Feature releases are frozen. All engineering effort shifts to reliability improvements—fixing bugs, adding redundancy, improving monitoring.
- Shared accountability: Product teams and SRE teams share the same budget. Product managers understand that pushing risky features consumes reliability budget.
Remediation & Permanent Safeguards
Calculation: If the SLO is 99.9% availability over 30 days: How it influences decisions: Practical implementation: The error budget transforms reliability from a vague goal into a measurable, actionable metric that balances innovation velocity with system stability.
- Track error budget burn rate on dashboards (Grafana/Datadog).
- Set alerts when 50%, 75%, and 90% of the budget is consumed.
- Automate deployment freezes when budget drops below a threshold.
- Error Budget = 100% – 99.9% = 0.1%
- In minutes: 30 × 24 × 60 × 0.001 = 43.2 minutes of allowed downtime per month
- Budget remaining (healthy): Engineering can deploy aggressively, run experiments, ship new featur...
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Issuing immediate kill -9 (SIGKILL) commands rather than allowing graceful termination via kill -15 (SIGTERM) when configuring team adopting practices SIGKILL immediately halts execution without allowing processes to flush memory buffers, commit database transactions, or remove stale PID locks.
-
Overlooking file system inode exhaustion (df -i) when diagnosing 'No space left on device' errors when configuring team adopting practices
Millions of small files or unrotated session tokens can exhaust available file system inodes even when standard disk storage (
df -h) shows ample free space. - Exhausting open file descriptor allocations (ulimit -n) under intensive concurrent socket connections when configuring team adopting practices Reaching file descriptor exhaustion throws 'Too many open files' errors, preventing services from accepting new TCP client socket connections.
-
Permitting defunct zombie processes to accumulate without fixing parent process SIGCHLD waitpid reaping when configuring team adopting practices
Zombie processes consume process table entries; accumulating zombies can exhaust the system maximum PID limit (
pid_max).