> ## Documentation Index
> Fetch the complete documentation index at: https://evalgate.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Inspect a trace

> Tree, timeline, tools, cost, scores, and evidence.

# Inspect a trace

Open any row in the Logs explorer to see the full trace. The detail page has
tabs, each reading the underlying records on demand.

## 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                |

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

## What to look for first

1. **Timeline** — find the long span. That is usually where time goes.
2. **Tools** — look for `error` rows. A tool failure often masquerades as a model
   failure.
3. **Cost** — a cost spike with few user-facing turns often means a hidden loop.
4. **Evidence** — if provenance is `incomplete`, this trace cannot be used as
   release evidence until the gap is fixed.

## Up next

[Save the view](./save-views) so you can return to this query.