Calling out a terrible on call system
summary
A company with ~15 developers and an SRE team of three breaks a single giant rotation into three rotations, assigns ownership of workers, alerts and monolith components to specific teams, and uses a code owners file in GitLab to auto-tag reviewers. On-call frequency rises from once every 3–4 months to regular cadence, incident response time drops, alerts get tuned, ownership increases, and developers are never alone because simultaneous on-call coverage and focused responsibilities actually work.
AI-written summary · about
chapters (6)
- 0:00Start
- 9:31Splitting App Ownership
- 13:03CODEOWNERS
- 14:38On-Call Training Sessions
- 23:41The Payoff
- 27:02Overhauling On-Call
related talks
19mOn-call revolution: Fostering ownership and collaboration
22mRaise a Production System:Making on-call human-scale w/ Observability & Trust
44mYou build it, you run it
31mHow to Build a Healthy On-call Culture
50mYou build it, you run it (why developers should also be on call)
26mBuild a data-driven on-call workflow for your team with atomic habits
27mYou Should Be On Call, too
16mHuman Centered On Call Practices