Site Reliability Evangelism: Practice Start-up within an Established...
summary
A yearlong SRE starter replaces one hire with a practical program: custody of an existing telemetry platform, synthetic checks wired to PagerDuty, and dashboards; a survey of 300 engineers reveals ~40–50 active incidents and very few postmortem actions closed, so postmortem policy changes to require reviews only for Sev1/2 and a SaaS incident tool is adopted. On-call expands from 2 to ~20 engineers across three business units, an effort pie (50/20/20/10) allocates time, monthly operational review rituals begin, and SLO work is prioritized using the DR plan as a roadmap.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:36A bit about us
- 2:44Dickerson's Hierarchy of Service Reliability
- 4:25Monitoring
- 10:38Incident Review - Changes Made
- 12:23Incident Response - On call
- 14:43Cultural Reinforcement
- 17:31Service Level Objectives
- 19:05The "Effort Pie"
- 20:26Operational Review Meetings
related talks
26mFrom Nothing to SRE: Practical Guidance on Implementing SRE in Smaller Organisations
51mThe Evolution of Site Reliability Engineering
28mEvolution of SRE and Rising Need of SRE Catalyzers
16mSRE in Transition: From Startup to Established Business
33mChallenges of Starting an SRE Team from Scratch in an Enterprise
28mHow to Do SRE When You Have No SRE
06mIGNITE: Want to start with SRE? Start with this talk.
41mBuilding an SRE Capability Inside a Large Organization