9 SLIs; Oh My!
summary
Proposes nine concrete SLIs grouped into three sets: customer/user experience, supporting services, and management/reputation. Gives concrete examples and numbers: an availability SLI defined as HTTP 200s with a target of 99.9% over a rolling 24-hour window, a checkout latency SLI of <750 ms with 99.999% monthly target, and recommends measuring Kafka broker health (CPU, timeouts, deadlocks), Kubernetes control‑plane latency, frontend paints and time‑to‑interaction, client device crashes, network packet loss, SaaS input/output, business KPIs, public sentiment and competitor benchmarks to fill error budgets and drive ops decisions.
AI-written summary · about
chapters (22)
- 0:00Intro
- 1:16What are SLIs
- 3:35Thinking of a good SLI
- 4:23Big caveat
- 4:50Golden signals
- 6:04N Murphy
- 6:33Themes
- 7:08Customer User Experience
- 7:49Application Metrics
- 8:45Frontend Metrics
- 9:33Device Monitoring
- 10:59Supporting Service SLI
- 11:43Infrastructure Metrics
- 12:52Network Metrics
- 13:19SAS Application Monitoring
- 13:46Management Reputation
- 14:23Business KPIs
- 15:47Public Sentiment
- 16:57Competitive Benchmark
- 17:55Conclusion
- 19:07Acknowledgements
- 19:55Quote
related talks
32m9 Things You Should Do When Starting to Use SLOs
37mReal World SLOs and SLIs: A Deep Dive
38mImplementing SRE practices: SLI/SLO deep dive
15mShit, our Site is Down! Let's build a culture of reliability
41mSLOs that Delight: Master Multi-Service SLO Calculations
37mRelia...bility?
30mMetrics for good, not evil
47mCultivating Production Excellence