Luke Angel
← back to the journal
Tag

#observability

5 entries
craft
The bug that wasn't in the mesh
“Write your root cause as a sentence you'd be willing to have your own logs contradict. Mine did, and the cure was 30 seconds of debug logging — not another rebuild.”
Jun 16
craft
Kill by message, not by ownership — and a node is a state
“Which OS process happens to own a node should have nothing to do with who's allowed to operate on it. A kill is a message, not a syscall.”
Jun 12
craft
Make the cross-mesh view honest
“A dependency graph is only as honest as the spans under it. If a service name is too coarse, nodes merge; if a receiver emits nothing, edges vanish; if you cc the observer, fake edges appear. Fix the emission, not the picture.”
Jun 05
craft
Watching a node boot, then a second mesh with no bridge
“A node that does work without leaving a trace is a bug. Start with the trace; everything else hangs off the spine it gives you.”
Jun 02
tools
What good IoT observability looks like in CloudWatch
“An IoT product without per-device-percentile latency dashboards is a product that doesn't know it's broken.”
Sep 11