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.
Speedscale Blog
Latest insights on API testing, performance optimization, and software development best practices from the Speedscale team.
The Three Pillars Were Built for Humans
Metrics, logs, and traces were built for humans and cheap storage. AI inverts both assumptions, and the next maturity level is a deterministic replay sandbox.
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.
Build WireMock mappings fast from real traffic
Skip hand-writing WireMock stubs. Speedscale records your real request and response traffic and exports it straight to WireMock mappings.
Five things your logs will never tell you
Logs, metrics, and traces are a lossy compression of production. Five things you can do with a traffic data lake that observability can't.
Fixing 403 auth errors when you replay traffic
Replay an authenticated flow and the protected calls fail with 403. Here is how proxymock recommendations fix the expired bearer token in one click.
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.
We won't train on your data is not a security architecture
MSA clauses and contractual guarantees aren't an architecture. If your production traffic leaves your cloud, you're trusting a policy, not a system.