What are the common Anti Patterns of SRE?
summary
Lists eight concrete anti‑patterns and how to fix them: renaming ops without changing work (don’t rebrand ops), SREs acting like level‑1 support, obsession with raw alert counts (teams cut 40 alerts and get measurable stability), SLAs that stop at server uptime instead of user journeys, missing observability and automated remediation, chasing snowflake VMs instead of immutable containers, dumping runbook work on SREs, and treating incidents as blame rather than blameless retrospectives.
AI-written summary · about
chapters (6)
- 0:00SRE introduction
- 6:54SRE role misconceptions
- 11:30SRE practices
- 20:05SRE anti-patterns
- 30:45Blameless retrospectives
- 32:09Q&A
related talks
47mPersistent SRE Antipatterns: Pitfalls on the Road to Creating a Successful
52mPersistent SRE Antipatterns: Pitfalls On the...
25mUnleashing the potential of SRE for modern operations
24mHow to Destroy an SRE
43mWhere SRE Can Go Wrong
30mWhen Is SRE Right For You?
42mDemystifying SRE and DevOps
58mEnterprise Roadmap for SRE
