From Telemetry to Traffic
Compare eBPF, sidecars, telemetry agents, OpenTelemetry, APM, and proxies through an evolving ladder of production visibility.
Read the guideObservability guides
API observability: find the problem and prove the fix
Metrics, logs, and traces tell you where to look. API traffic shows the request, response, and dependency behavior that caused the failure. These guides connect the two.
Start here
How the layers of production visibility fit together
Choose what you need to do
Understand the gap
Learn what metrics, logs, traces, and traffic each reveal about a production problem.
Diagnose a live problem
Follow practical workflows for latency, retries, and failures across service boundaries.
Turn findings into tests
Carry production evidence into repeatable tests that run before the next release.
All observability articles
eBPF: Correlating rustls Plaintext to TCP Connections Without a File Descriptor
Follow an eBPF debugging trail through rustls, Tokio inlining, and an empty map to learn how TLS plaintext gets matched to the right TCP connection.
Five Ways to Use OpenTelemetry Beyond Observability
Teams run inventory, security logs, request routing and billing through OpenTelemetry. Five non-observability uses, and the failure mode of each.
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.
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.
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.
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.
The Pod Was Cheaper. The Service Wasn’t.
Use OpenCost and proxymock to prove Kubernetes rightsizing lowers cost per successful request without hiding behavior or throughput regressions in testing.
Flamegraphs Find It. Replay Proves It.
Use Grafana Pyroscope and proxymock with an AI coding agent to find a Go CPU hotspot, preserve API behavior, and verify the performance fix.
Go from alert to reproducible test
Capture the API traffic behind a production issue, replay it safely, and verify the fix against the same behavior.