From Telemetry to Traffic
Compare eBPF, sidecars, telemetry agents, OpenTelemetry, APM, and proxies through an evolving ladder of production visibility.
Posts about developer tools
Browse 83 posts in this category
eBPF: Preventing Garbage HTTP Payloads When Reading Kernel Scatter-Gather Buffers
How our nettap eBPF agent produced garbage HTTP bodies from kernel iov_iter scatter-gather buffers, and the CO-RE plus task-local storage fix that made it correct.
The Best Model Is a Routing Decision
The best model isn't the smartest — it's whichever should get the next unit of work. Notes from NVIDIA on routing, local models, and the AI factory.
Two confident fixes missed this production bug
A production bug survived two confident fixes and green tests. Replaying the captured request exposed the missing state and proved the real fix.
Trace without traces
The trace was sampled out. I found the bug anyway — by filtering recorded traffic on the customer's email instead of a trace ID. Here's how to follow one request across four services with no trace IDs and no OpenTelemetry.
Which Bugs AI Agents Fix Better With Traffic
A second run of our AI bug-fixing benchmark shows where captured traffic lifts agents toward 90%, why service maps barely help, and which bugs still fail.
Beware of PII in Testing Data: The Security Iceberg and Where PII Actually Hides
Using 'production-similar' data in pre-production is a major security risk. Learn why traditional masking fails, where hidden PII hides, and how to fix it.
Capture once, test forever
Production traffic is the most complete record of what your system does, and most teams throw it away. One capture powers reproduce, validate, and sandbox.
Logs told me something broke. Traffic showed me what.
Capture production traffic and store it in your own Elasticsearch with Speedscale BYOC. Pull it locally with es-gather.py and reproduce bugs with proxymock.
Try Speedscale free
Choose the desktop proxymock or the hosted cloud trial to get started.