14h ago · 9 min read · A team I worked with tried to build their billing system on top of their tracing pipeline. The idea was clean: every operation already generates a span; spans already have duration and attributes; adding user_id and billable_units to each span lets f...
Join discussion2d ago · 3 min read · "What Calls What?" The question that launches a thousand Slack threads. In every microservices architecture I've worked with, nobody has a complete picture of how services interact. Service maps fix this. The Problem With Static Diagrams Every team h...
Join discussion
3d ago · 8 min read · As developers, we all have a favorite debugging tool: console.log. It is simple, it is fast, and it gets the job done when we are trying to figure out why a variable is undefined on our local machine. But the habits we build in development can become...
Join discussion
2d ago · 3 min read · The $50K/Month Monitoring Bill I audited our monitoring stack last quarter. The total cost across all tools: $52,000/month. For a company with 200 engineers. That's $260 per engineer per month just to watch our systems. Something had to change. Where...
Join discussion3d ago · 3 min read · $12,000/Month for Logs Nobody Reads Our logging bill was $12,000/month. We were ingesting 2TB/day. When I asked the team what percentage of logs they actually looked at during incidents, the answer was embarrassing: about 5%. We were paying to store ...
Join discussion4d ago · 21 min read · A note on the code in this article. The observability setup shown here is derived from a production BFF built for a Norwegian enterprise education platform. Resource names, workspace identifiers, aler
Join discussion
