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.
Posts about observability
Browse 21 posts in this category
The Kubeshark Workflow That Doesn't Stop at the Dashboard
A Kubeshark alternative that goes beyond observability. Stream live cluster traffic into proxymock, then replay or mock it locally from your laptop.
Replay Real Customer API Sessions as Datadog Synthetics Tests
Export recorded proxymock traffic to Datadog Synthetics in one command. Auth headers redacted, global variables created. No scripting, no flaky journeys.
Replace API Synthetics with Traffic Replay
UI synthetics only tell you something is broken. Traffic replay per microservice isolates failures before any human walks up. Zero scripts required.
OpenTelemetry Trace Testing for CI Release Gates
Trace-based testing uses OpenTelemetry traces as replayable test input so CI catches production regressions before deploy, not after incident review.
When Your Observability Literally Stops Traffic
Observability tells you what failed—but not how to recreate it. Why reproducibility is the missing fourth pillar, and what that means for incident response.
From Datadog to CI Tests: Catch Regressions Before Deploy
Learn a practical workflow to convert Datadog metrics, traces, and incidents into CI tests that catch regressions before deploy.
The 4 Golden Signals of Monitoring Explained
Learn the 4 golden signals — latency, traffic, errors, and saturation — and how to use them for monitoring, alerting, and pre-release testing.
The Observability Gap: Why Monitoring Data Should Drive Tests
Teams spend six figures on observability but test with synthetic data. Close the gap between what you know about production and what you validate pre-release.