SRE & Observability
Reliability as something you can measure: SLOs and error budgets, multi-burn-rate alerts, the four golden signals, incident severity and a definition of "recovered" that holds up. Plus observability on eBPF and OpenTelemetry — and traps like HTTP/2 on internal traffic that only surface under load.
-
HTTP/2 for Internal Traffic: A Well-Known Class of Pitfalls
One connection for every request, a shared flow control window, and a pool that never evicts the dead: why HTTP/2 services hang "without errors" and what Go and gRPC did about it.
-
Observability 2.0: eBPF, OpenTelemetry, and AI that finds the root cause
Instrumentation moved into the kernel, telemetry into the OTel standard, root cause analysis toward the machine. Three shifts and the order in which they pay off.
-
An incident closed twice: severity, ICS roles and three gates
Why «recovered» is the most expensive word in an incident, and the three checks that must pass before you say it.
-
Four golden signals: what they actually catch and why the stack is VictoriaMetrics + Loki
What each of the four signals really catches, and three traps where «we have monitoring» turns out to be green checkmarks above a broken service.
-
Error Budget as a Stop Button: SLOs Without Panic
Error budget turns reliability into a resource you can spend — and multi-burn-rate alerts turn it into a page that's actually worth waking up for.