Inside the .NET Garbage Collector: Generations, the Card Table, and Tuning That Actually Works
Most developers treat the garbage collector as weather: it happens to them, and occasionally it ruins their day. But the
Tag: Observability
SLOs and Error Budgets: The Math That Decides When to Ship and When to Stop
Every team says they care about reliability, but very few can answer the follow-up question: how reliable, exactly, and how
Continue readingSLOs and Error Budgets: The Math That Decides When to Ship and When to Stop
Trace Context Propagation: Why Your Distributed Traces Break and How to Fix Every Hop
You open your tracing backend to debug a slow checkout request and find five disconnected traces instead of one. Five
Prometheus Metric Cardinality: How Explosions Happen and the Five Controls That Stop Them
Every Prometheus failure I’ve seen in production started the same way: someone added a label. A user ID on a
Structured Logging in Go: slog, OpenTelemetry, and the Fields That Matter in Production
At 02:14 on a Sunday, an alert fires: payment success rate dropped four percent. You run kubectl logs across a
SLOs and Error Budgets in Practice: Building Reliability You Can Alert On
Your service was up 99.95% of the time last month. Great number — until you realize that users filed complaints
Continue readingSLOs and Error Budgets in Practice: Building Reliability You Can Alert On
Go GC Tuning with GOGC and GOMEMLIMIT: A Practical Guide for Containers
Every Go program ships with a garbage collector, and most run happily with the defaults. That changes the moment you
Continue readingGo GC Tuning with GOGC and GOMEMLIMIT: A Practical Guide for Containers
Distributed Tracing in Go with OpenTelemetry
When a request crosses five services and the latency budget blows up, a single log line rarely tells you where
Continue readingDistributed Tracing in Go with OpenTelemetry
Prometheus Cardinality: The Label Decisions That Decide Whether Your Monitoring Survives
Every Prometheus failure I have debugged that was not a network problem eventually came down to the same thing: too
SLOs You Can Actually Alert On: Error Budgets and Burn Rates in Prometheus
Every on-call rotation has a story about the alert that fires at 3 a.m. for something that isn’t wrong. CPU
Continue readingSLOs You Can Actually Alert On: Error Budgets and Burn Rates in Prometheus