# Traces

A paginated, low-level list of per-trace summaries with duration, cost, and models — for looking up a specific trace.

The **Traces** page lists per-trace summaries for a service. It's the lowest-level view Brizz offers and exists mainly for one job: you have a trace id from a log line or an error report, and you want the trace behind it.

:::info
Traces is off by default. If **Traces** isn't in your navigation, [contact us](mailto:support@brizz.ai) — it isn't a setting an organization admin can change. Most teams don't need it: [Sessions](/docs/platform/sessions.md) is the view built for reading agent behavior.
:::

## What it is

One row per trace. Each aggregates a trace's spans into a summary; what it doesn't do is group traces into a [session](/docs/introduction/concepts.md#session), which is what the Sessions page is for.

## How it's populated

From ingested telemetry, summarized per trace, with no quality-analysis step in between.

## How to read it in the dashboard

Pick a service, then use the date range and pagination. Each row shows timestamp, cumulative span duration (summed across spans, so parallel work can exceed elapsed wall-clock time), cost, and models used. Open a row for its span tree, which loads up to 5,000 spans.

:::warning
The search box filters only the rows already loaded on the current page — it does not query the backend. A trace that exists on another page reads as missing, so page through or narrow the date range instead of trusting an empty search.
:::

## How to act on it

1. **Come here with an id, not a question.** For exploring, [Sessions](/docs/platform/sessions.md) is faster — conversation, timeline, and metrics in one place.
2. **Rule out the page before blaming ingestion.** Search is page-local, so check the service, date range, and later pages first. Only then is a missing trace evidence of an ingestion problem — see [Troubleshooting](/docs/help/troubleshooting.md).

## Availability

Off by default, and enabling it is handled by Brizz rather than by an organization admin. The setting removes Traces from the navigation; it doesn't block the URL, so a direct link can still render for someone who has access.

## See also

- [Sessions](/docs/platform/sessions.md) — the conversation-level view, and the one to reach for by default.
- [Core concepts](/docs/introduction/concepts.md) — how traces, spans, and sessions relate.
- [Troubleshooting](/docs/help/troubleshooting.md) — when a trace you expected never arrives.