Distributed tracing
Where in the call did it break — and was it treatment?
OTLP-native distributed tracing on the same pipeline as your flags. See the shape of a request as a waterfall and flame graph, and — uniquely — filter to the slowest traces from the treatment group, because every span is stamped with the flag and variation its unit was in.
FreeIncluded from the Free tier.
POST /checkouttrace · 240 msThe exact hop that broke — in release context.
What you get
Why Foredeck for tracing.
OTLP-native, one-line adopt
OTel collectors, auto-instrumentation, and existing tracing SDKs point at Foredeck with an exporter change.
Exposure-stamped spans
Every span carries the flag/variation trace-wide — the one join no standalone APM can make.
Waterfall, flame & service map
See the request shape, a per-service dependency map with RED metrics, and a per-endpoint drill-down to its traces.
Trace-based metrics & sampling
Exact counts and error rates under sampling from an unsampled rollup, with keep-on-error / keep-slow tail rules.
How it works
Three steps, one pipeline.
Send OTLP spans or use the SDK’s tracing API — the current flag/variation is auto-attached.
Open the trace as a waterfall/flame graph and read the span that regressed.
Filter to the slowest treatment traces, and pivot to logs and the flag.
Better together
Works with the rest of the platform.
Logs
FreeSearch logs in release context — OTLP-native, correlated to flags.
Explore Logs →Services & SLOs
FreeGolden signals and SLOs per service and endpoint.
Explore Services & SLOs →Product Analytics
FreeThe front-end story: page views, clicks, Web Vitals — joined to variations.
Explore Product Analytics →Guardrails & Auto-Rollback
ProCatch a regressing release before it spreads — automatically.
Explore Guardrails & Auto-Rollback →One object, one pipeline. The same rollout you ship is automatically measured, guarded, and — when it breaks — traceable, because every signal is joined to the flag and variation the unit was in.
Get in