Inspect a trace

The tabs

Tab	What it shows
Tree	The nested span hierarchy — the shape of the call
Timeline	Spans on a time axis, so you can see what ran in parallel and what blocked
Thread	The message turns between user, assistant, and tools
Input / Output	The exact request and response payloads
Tools	Every tool call, its arguments, result, and any error
Scores	Scorer outputs attached to this trace, with version and hash
Cost	Token usage and cost, linked to the model-call ledger
Evidence	Provenance state — complete or incomplete — and what is missing
Review	Any review task, decision, and rationale tied to this trace

When a collection has more than 100 records, use its Load more control until the continuation is complete. The counts are exact, not estimates.

What to look for first

Timeline — find the long span. That is usually where time goes.

Tools — look for error rows. A tool failure often masquerades as a model failure.

Cost — a cost spike with few user-facing turns often means a hidden loop.

Evidence — if provenance is incomplete, this trace cannot be used as release evidence until the gap is fixed.

The tabs