Prod Detectives: Solving the Case Before the Crash
summary
Practical guidance from an OVHcloud engineer on diagnosing and resolving production incidents fast using concrete troubleshooting methodology. Covers logging, monitoring, and team organization practices and tools to turn incidents into methodical investigations so small on-call teams can find root causes quickly.
AI-written summary · about
chapters (14)
- 0:00Incident management intro
- 2:07Run and stress in prod
- 9:42Run point of contact
- 10:44Troubleshooting method
- 15:53Restore service first
- 22:07Typical run cases review
- 25:37Post-incident docs importance
- 26:39Designing maintainable apps
- 27:21Structured logging best practices
- 31:36Effective monitoring metrics
- 35:30App errors and auto alerts
- 37:57Continuous improvement and tech debt
- 40:44Linters and code conventions
- 41:47Conclusion and resources
related talks
40mProduction Detectives: Solve the Case Before the Crash
39mHow to Use Common Investigation Practices in Troubleshooting
41mDetective Hat: Investigating Production Issues
39mResolving Outages Faster with Better Debugging Strategies
22mAfter the dust has settled: learning from incidents
39mWhat a full production crash taught us
19mHow to handle incidents at scale
29mShrinking the Impact of Production Incidents
