From Telemetry to Traffic
Compare eBPF, sidecars, telemetry agents, OpenTelemetry, APM, and proxies through an evolving ladder of production visibility.
Read the guideObservability guides
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
Compare eBPF, sidecars, telemetry agents, OpenTelemetry, APM, and proxies through an evolving ladder of production visibility.
Read the guideLearn what metrics, logs, traces, and traffic each reveal about a production problem.
Follow practical workflows for latency, retries, and failures across service boundaries.
Carry production evidence into repeatable tests that run before the next release.
Stream captured API traffic into Apache Iceberg with Speedscale BYOC. Set up AWS S3 Tables and query deduplicated HTTP errors in DuckDB.
Follow one checkout across three session IDs. Run the linked sessions lab in proxymock and see which requests belong to each shopper and why.
Design a traffic replay system that catches wrong responses. Connect recordings, state isolation, response checks, and CI gates with a proxymock example.
This how-to video shows how to use Speedscale's full-text traffic search to instantly find where a specific piece of data appears as it flows through your.
Export a recorded API session to Datadog Synthetics with proxymock. Review step limits, variable chaining, credentials, and assertions before publishing.
Discover endpoints, RED metrics, and traces in an opaque Kubernetes service with OpenTelemetry eBPF Instrumentation, then replay traffic with proxymock.
A Kubeshark alternative that goes beyond observability. Stream live cluster traffic into proxymock, then replay or mock it locally from your laptop.
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.
Inspect encrypted microservice traffic with Speedscale’s eBPF collector. Check TLS support, node permissions, and Java-agent rollout requirements first.
Capture the API traffic behind a production issue, replay it safely, and verify the fix against the same behavior.