You build it, you run it.
summary
Sentry describes a shift to You Build It, You Run It after an ingestion pipeline incident (Incident 27) that degraded for about 12 hours and required writing code to fix. Engineering teams adopt SLOs, a centralized SLO dashboard, and require incident follow-up as milestones tied into performance reviews; directors cover on-call gaps. The claim: operational ownership grows engineers’ skills and reduces repeat outages by forcing measurable accountability.
AI-written summary · about
chapters (7)
- 0:00Introduction and Personal Journey
- 0:30Understanding 'You Build It, You Run It'
- 4:34The Challenges of Implementing 'You Build It, You Run It'
- 6:13Learning from Past Incidents
- 8:53How we do YBIYRI at Sentry
- 13:51Wrap Up - Accountability is the key
- 17:46Q&A Session
related talks
26mIncreasing the collaboration between SREs and Developers
44mYou Build It You Run It sounds great... but it won’t work here!
30mHow Did Things Go Right? Learning More from Incidents
22mA Dual Approach to Accountability Engineering
23mSite Reliability Evangelism: Practice Start-up within an Established...
44mYou build it, you run it
14mRun, Walk, Crawl, or How We Failed Our Way to SLO Readiness
26mDouble, Double, Toil and Trouble!