[webservice] [debugging] [monitoring] [honeycomb]
We have many tools at our disposal to manage and monitor systems and applications: Logs, Data, Dashboards, Monitoring, Test systems, and more.
While all of these things are helpful, they all create more work. None of us need more work to do.
Debugview (and the OutputDebugString that populates it) is super handy and is the tool of choice for many of us. The problem with Debugview is that you can’t leave it running all day. It sucks up ram and CPU, particularly in high volume situations.
These things hounded me. I have 3 API servers (or 5, depending on the context), 6-7 web servers and while I can RDP into any of them to open Debugview and see what’s going on – I have to KNOW that something is going on.
That points us at notifications – but all they do is make sure that we’re the first one who knows about the problem (usually).
Bottom line, all of these servers and the cognitive load they place on you with their incessant “Hey, I’m doing this”, “Hey, I’m doing that”, and “Hey I’m not feeling too good, better give me some attention” ended up leading me down the path to a solution, which exposed another situation.
The ultimate solution I found, the situation I discovered, and the current state of the solution I created to cure my situation are the real subjects of Arnold’s 2019-2020 double feature birthday webinar. It’s a double feature because it has 31 more slides than the largest slide deck I’ve ever presented from (the previous max was 3).
If you’re spinning plates to keep everything running, this might be a helpful webinar for you.
0:00 - Start
0:05 - Introduction
0:19 - Mark Starts