Getting Back to Sleep ASAP for the On-Call Developer

on YouTube ↗25m

" summary

A concrete postmortem of an on-call incident that adds runtime instrumentation to a live JVM, extracts and correlates a user transaction ID across services, and pivots from logs to traces to locate a faulty billing call. Shows Lightrun-style live debugging: injecting probes, creating short-lived dashboards, and validating a rollback, ending with the service restored and the on-call rota unpaged so the team can return to sleep.

AI-written summary · about

" chapters (9)

1. 0:00Start
2. 0:27Introduction
3. 3:14On-call challenges
4. 8:30Debugging strategies
5. 13:12Handling incidents
6. 17:08Real-time troubleshooting
7. 20:38Post-incident learning
8. 23:25Preventing issues
9. 24:27Q&A

" related talks

• 25mGetting Back to Sleep ASAP for the On-Call DeveloperTom Granot · Conf42 Enterprise Software 2021
• 50mYou build it, you run it (why developers should also be on call)Chris O'Dell · NDC London 2018
• 44mYou build it, you run itChris O'Dell · Agile on the Beach 2018
• 05mOn-Call in a World Full of ToilJay Gordon · DevOps Days Toronto 2019
• 31mHow to Build a Healthy On-call CultureSerhat Can · DevOpsDays Boston 2019
• 30mOn call does not have to suckCharity Majors · LeadDev Berlin 2022
• 26mDebugging Clojure Services Under StressPaul Lam · Clojure/north 2020
• 22mRaise a Production System:Making on-call human-scale w/ Observability & TrustChris Sun · ScaleConf Colombia 2019