Pepperoni, Puppets, and Priorities: Demystifying SLAs, SLOs, and SLIs
summary
Argues that prioritization must hinge on measurable customer-facing claims not vague topics, using a pizza metaphor: define SLIs like order accuracy and delivery time, pick SLOs (example threshold 95%), and treat SLAs as contracts with an or else; observability can be third‑party (mentions datadog) or a built product; use error budgets/Code Orange to halt features when reliability breaks; platforms are products that get stitched together and must prove they work.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:09Why SLAs SLOs and SLIs matter
- 2:33Sock puppet play on priorities
- 3:56Software quality and value
- 13:08DevOps beyond Dev and Ops
- 20:39Evolving DevOps definition
- 36:28Product management is DevOps
- 37:32Defining SLAs SLIs and SLOs
- 47:37Prioritizing work with SLAs SLOs and SLIs
- 51:12Q&A on pizza preferences
- 54:00Q&A on decision-making
- 1:03:10Closing remarks
related talks
35mAvoiding Goodhart's Law - Use SLO's as Tools Not Cudgels
28mLean Product Development Through SLOs
06ma pint sized introduction to SLO
30mMetrics for good, not evil
37mReal World SLOs and SLIs: A Deep Dive
38mImplementing SRE practices: SLI/SLO deep dive
29mMeasuring Reliability: What Got Us Here Won't Get Us There
32m9 Things You Should Do When Starting to Use SLOs