In the old days, production was the machine we could kick. We could all check what was going on, debug, fix and observe. This was problematic and DevOps, SRE, etc. took the front stage. That's good. But it also has negative implications and Developer Observability is here to fix that.
"Debugging is twice as hard as writing the code in the first place"-Brian Kernigham Debugging production is harder! To make matters worse, containerization & orchestration made debugging even harder. In this talk we review the debugging of a production app deployed with k8s with kubectl debug & more
Brian Kernigham said: “Debugging is twice as hard as writing the code in the first place.” In fact, debugging in a modern production environment is even harder - orchestrators spinning containers up and down and weird networking wizardry that keeps everything glued together, make understanding systems that much more difficult than it used to be. And, while k8s is well understood by DevOps...
Production bugs are the WORST bugs. They got through unit tests, integration tests, QA and staging… They are the spores of software engineering. Yet the only tools most of us use to attack that vermin is quaint little log files and APMs. We cross our fingers and put on the Sherlock Holmes hat hoping that maybe that bug has somehow made it into the log… When it isn’t there our only remedy is...
When a production problem happens all bets are off. We'll do anything to "save" production and get us back on track. But by then it's too late. If the logs don't have this information already then we need to add new logs. That means running the full test cycle again, updating servers and hoping that this time we'll see the issue. This is bad. Production bugs cost us money. Both in engineer time...
Priority access to all content
Video hallway track
Community chat
Exclusive promotions and giveaways