Improve Service Reliability
12 weeks · 4 milestones
Milestone map
Milestone map
3 milestones
Define Service Level Objectives (SLOs) for at least two critical user-facing services — specifying the SLI (what is being measured), the SLO target (e.g. 99.9% availability over a 30-day rolling window), and the error budget derived from it. Measure the current reliability baseline by computing actual SLI values over the past 30–90 days using existing monitoring data. Produce an error budget report showing current error budget consumption and the reliability gap between actual and target.
Proof required
Submit an SLO definition document covering at least two services, with for each: the SLI definition (what is measured and how), the SLO target (percentage and time window), the error budget calculation, and the current actual SLI value from 30–90 days of historical monitoring data. Include a brief error budget report showing consumption rate and projected budget exhaustion timeline if current trends continue. ADVERSARIAL VERIFICATION: a named SRE, platform engineer, or engineering director (5+ years experience) must read the SLO definitions and provide written feedback confirming that the SLIs are meaningful user-experience proxies and not gaming-prone internal metrics.
What gets checked
- SLO definitions for ≥2 services, each with SLI, target, error budget, and actual baseline measurement
- Error budget report showing consumption rate from real monitoring data — not hypothetical values
- Reviewer feedback confirming SLIs are genuine user-experience proxies