My Life as a Solo SRE
Talkat SREcon19 Europe/Middle East/Africa · on Wednesday, 2019-10-02· at 15:00· Track 2: The Liffey A·
summary
2015 shows repeated outages, bad releases and frantic paging so the company creates a solo SRE role in 2016 and applies concrete changes: defines SLIs and SLOs, builds dashboards tied to customer conversations, enforces error budgets and moves developers onto the support rota. noisy alerts are deleted, playbooks and runbooks are written, MTTA/MTTR improve, mean time between failures rises and support tickets and pages drop; the startup is acquired by Frisco late 2016.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 2:00Loud Clock
- 3:44Problems
- 5:05Alerts
- 7:35Is everything wrong
- 8:12I got paged
- 9:12Im not shy
- 10:44The madness phase
- 11:14SLeyes
- 11:52SLos
- 12:39Dashboards
- 13:15Reliability
- 13:46Availability
- 14:09Valuebased conversation
- 14:46Accountability
- 15:13Sharing knowledge
- 15:58Getting developers on board
- 16:30Business side of the house
- 17:02Turning it around
- 17:27What didnt go so well
- 18:30Conclusion
- 19:24Questions
related talks
18mThe Good, the Bad and the Ugly: The 3 Learnings of an SRE
28mEvolution of SRE and Rising Need of SRE Catalyzers
31mConfessions of an SRE Manager
33mMy Journey to SRE
13mSucceeding as the Lone SRE in a Small Team
27m20 Years of SRE: Highs and Lows
13mWhat To Do When SRE is Just a New Job Title?
24mManaging Up and Sideways as an SRE