Cultivating Production Excellence
summary
Defines production excellence as measurable practices: set 99.9% over 30 days SLOs (example: HTTP 200 and <100ms), compute the error budget (one in a thousand allowed failures; e.g., 100M events → 100k failures/month) and use SLO-driven alerting to silence noisy dashboards. Build observability that lets engineers ask new questions in production, standardize tooling (recommend open telemetry), run game days, keep blameless postmortems, and prioritize the top three risk mitigations by expected bad-user impact.
AI-written summary · about
chapters (10)
- 0:00Introduction and welcome
- 1:49Complexity in production systems
- 3:55Why not to buy DevOps
- 8:05Production excellence over ownership
- 10:11Knowing when systems are too broken
- 17:33Debugging production failures
- 21:08Collaboration across teams
- 24:40Learning from past outages
- 27:53Systemic risks in observability
- 28:55Summary and call to action
related talks
47mCultivating Production Excellence
58mCultivating Production Excellence
03mCultivating production excellence
39mShifting Left on Production Excellence with Observability
25mHow to detangle and understand production
29mReducing Trauma in Production
19mThink Prod Up Front: Shifting Left on Production Excellence
51mShrinking Production Incidents