Product · Traces

Move from service topology to the failing span.

Explore service health, RED metrics, latency distributions, error-first traces, and complete span waterfalls in one workflow.

Trace exploration with the surrounding system intact.

Understand which service changed, which request failed, and what the rest of the stack recorded.

Derive topology and service health from traces to see dependency paths and degraded nodes.

Use rate, errors, and duration as the first filter before opening individual traces.

Prioritize failed and slow operations, then inspect the complete span waterfall.

Keep the trace connected to logs, metrics, profiles, services, and the current investigation frame.

workflow

Move from broad service behavior to the smallest useful unit without losing the path back.

101 · Map
See the service dependency path
Identify degraded or failing nodes and the request rate moving through each edge.
202 · Prioritize
Filter slow and failed traces
Use latency distribution and error state to focus on representative requests.
303 · Inspect
Read the span waterfall
See where the critical path spent time and which downstream operation returned the failure.
404 · Corroborate
Open related logs, metrics, and profiles
Continue with the same trace, span, service, and time context in the investigation stack.

proof / shipped

Service graph, RED metrics, trace detail, and server-side correlation routes are part of the current API and UI.

Product · Traces

Explore service health, RED metrics, latency distributions, error-first traces, and complete span waterfalls in one workflow.