How to Do SRE When You Have No SRE
Talkat SREcon19 Europe/Middle East/Africa · on Thursday, 2019-10-03· at 14:00· Track 2: The Liffey A·
summary
Recommend committing one to two hours a week to SRE work, running quick reviews that document worst-case failure modes, capacity headroom, access lists, infrastructure diagrams, backups and third‑party contacts; create small 1–2 hour tasks (e.g. test a backup, rebuild a mystery host, add a Slack deploy hook) and record them in a wiki and calendar; use blameless incident reports with templates and exec sponsors; expect incremental wins (quarterly rebuild practice, fewer surprises) rather than overnight staffing changes.
AI-written summary · about
chapters (25)
- 0:00Intro
- 0:30Why are you here
- 2:15TLDR
- 3:30How is this different
- 4:03Cya
- 5:06Review
- 5:54Capacity Requirements
- 7:04Security
- 8:36Calendar
- 9:15Infrastructure
- 11:54Third Parties
- 13:58DomainsSSL Certs
- 15:54Releases and Updates
- 17:59What to do now
- 18:30Rules
- 18:55Publish Your Rules
- 19:29Rural Examples
- 20:15No Downside
- 21:55No Blame
- 22:09No Human Error
- 23:20Its okay to not be okay
- 23:54Code changes
- 24:10Network issues
- 24:54Keep going
- 25:38Questions
related talks
25mUnleashing the potential of SRE for modern operations
30mWhen Is SRE Right For You?
24mHow to Destroy an SRE
52mI’m SRE and You Can Too!—A Fine Manual...
22mSRE for Enterprises
27mGetting Started with SRE
38mThe Smallest Possible SRE Team
23mSite Reliability Evangelism: Practice Start-up within an Established...