Be prepared for production incidents
summary
Shows a concrete incident playbook: a GitHub runbook repo with step-by-step commands, a monitoring stack using Sentry, Prometheus and Grafana, and on-call routing via PagerDuty. Demonstrates running quarterly chaos drills against staging, a scripted automated rollback that cuts failed-release MTTR from about 90 to 15 minutes in examples, and a checklist for toggling feature flags, restoring backups, and communicating to users. Varik's GitHub: https://github.com/var77
AI-written summary · about
chapters (5)
- 0:00Introduction
- 3:09Incident narratives
- 9:39Maintenance mode applications
- 17:31Example scenarios
- 20:54Environmental factors
related talks
15mIncident Ready: Chaos Engineer Your Incident Response
20mPremiere
45mWhat to do when complex systems fail: A guide to chaos management
51mPatterns & Playbooks to Make Every Commit Production Ready
31mTesting in Production
26mMission Critical Mindset Building a Culture of Resilience in DevOps Teams
29mEngineering Chaos for Resilient Applications: A Gameday Guide
32mOperating Rails: what about after you deploy?