Getting Back to Sleep as Soon as Possible for the On-call Developer
It's the middle of the night and there's much ado about nothing. Well, not quite about nothing - there's definitely something happening: One of the services your team owns is crashing. And by crashing, I mean sometimes crashing. It's not really that bad, but it's bad enough for the floodgates to open and for the DevOps folks to lose their marbles and ping you relentlessly on Slack. Ping. Ping. Ping.
This talk is all about that feeling, and what we can do to make the whole situation suck less when it inevitably comes up again. We will walk through a close-to-real life incident from the perspective of the on-call developer, and discuss practical and technical steps developers can take to increase observability while on-call (even when a serious, hard to debug issue arises).