One-shot cross-signal pivot for a trace id.
Given a trace id, returns (all fields top-level, no nested summary object):
rootOperation, spanCount, errorCount, totalDurationNanos, startTime — trace summary
spans — every span in the trace (up to 1000)
logs — logs tagged with that traceId (no window limit, up to 1000)
exemplars — metric exemplars whose traceId matches, within the span window (up to 1000)
windowFrom / windowTo — the derived scan window (earliest span - 5s / latest span end + 5s)
The window is derived from the trace's spans. If the trace is unknown, spans and
exemplars are empty but logs are still returned if they carry the traceId. Exemplar
filtering is window-bounded; log filtering is not.
Use this as the primary entry point when you have a trace id and want to see all
correlated signals at once. Returns core fields by default; verbose=true flattens
attributes in for both spans and logs (plus a `resource` object) and long string
values are capped. Use run_sql for raw columns or custom selection. After
reviewing the result, drill into individual signals with logs, spans, or metrics as
needed.
Long-lived traces (scheduler ticks, batch jobs) can produce very large verbose
responses even with the caps. Prefer verbose=false first; for error triage,
the logs tool with traceId + level is a cheaper, targeted alternative. Pass
maxStringChars to tighten string truncation per call.
Returns: traceId, traceUrl, rootOperation, spanCount, errorCount, totalDurationNanos,
startTime, windowFrom, windowTo, spans[], logs[], exemplars[], queryStats. traceUrl
is a shareable Fixter UI link for this trace — attach it when citing the trace as
evidence to the user.