Your Observability Stack Found the Fire. Congratulations.
Observability tells you when production is on fire. Capturing and replaying real traffic lets you recreate the incident, verify the fix, and keep it fixed.
Posts about observability
Browse 37 posts in this category
Reliability Engineering in the AI Era
See why reliability engineering must span code, testing, telemetry, and incidents as AI agents erase the boundary between pre-production and production.
From Telemetry to Traffic
Compare eBPF, sidecars, telemetry agents, OpenTelemetry, APM, and proxies through an evolving ladder of production visibility.
Explain Non-CPU Latency With Prometheus + proxymock
Diagnose a p95 latency regression that CPU profiling cannot explain using Prometheus histograms, then prove the fix with identical proxymock replays.
Reproduce A Rare Retry Path With Loki + proxymock
Find the rare payload that sends a service down a retry path, correlate it to the recorded response, and prove the fix with proxymock replay.
Separate Application Latency From Network Failure With Hubble
Use Cilium Hubble flow evidence and proxymock replay to prove whether a Kubernetes timeout came from your code, a dependency, or a dropped packet.
Synthetic Monitoring Is Broken. Your Production Traffic Can Fix It.
Synthetic monitoring depends on scripts engineers maintain by hand. Capturing and replaying real production transactions turns customer behavior into tests.
Observe Opaque Services With OpenTelemetry eBPF + proxymock
Discover endpoints, RED metrics, and traces in an opaque Kubernetes service with OpenTelemetry eBPF Instrumentation, then replay traffic with proxymock.
Diagnose Serial N+1 API Calls With Tempo + proxymock
Diagnose serial N+1 API calls with Tempo and proxymock. Replay recorded traffic, inspect trace windows, and prove a concurrency fix preserves behavior.