Skip to content
GitHub
Start a 14-day trial

Traces

Traces is where you go from a finding to the requests behind it. It opens on recent traffic, and each of the three explorers — Traces, Logs and Metric Explorer — shares the same layout, so learning one teaches you the others.

It lives under Exploration → Traces. You usually arrive here from Critical Paths or Metric Signals, which hand off a query already scoped to what you were looking at.

  • A query bar that takes plain English. Type “slow failed checkout requests” and press Interpret: the sentence becomes filter pills you can edit, and the query runs. The filter controls sit right below, always visible. See Ask in plain English.
  • A results area with a Chart / Table / Both toggle (Both by default), charted from the rows you fetched.
  • An Insights rail on the right, open by default, summing up those rows: totals and what stands out.

The time range offers 15m, 1h, 3h, 24h and 7d. It opens on 1h the first time, then on the last range you picked in any of the three explorers.

The query rides in the page address, so Back, refresh and a shared link all restore the same filters and time range. Save keeps a query under a name, and Saved queries… runs it again later.

Traces filters on the R.E.D. signals — Rate, Errors and Duration — plus Services and Endpoints (endpoints narrow to the services you pick). Results come as a table with a Traces / Spans / Errors / Avg Duration / Services summary bar and a Group by Trace toggle that flips between individual spans and whole traces.

From any row you can open the trace timeline, view its details, or filter by this row to pivot the query.

The timeline is a waterfall with a span tree you can expand and search. Switches above it turn on Show Critical Path (the lightning bolt), Show Errors Only and the minimap (Map). The logs that share the trace’s ID sit in a panel below the waterfall; open it, or click a span’s log count. Press Analyze for a written read of where the time or the error went, or Copy for agent to hand the trace to your own coding agent.

To hold one trace against another, use Compare traces.