Skip to main content
The Traces page lists recent traces for the project and lets you drill into any one.

​
Trace list

Each row summarizes a trace: name (root span), start time, duration, span count, error count, services, total tokens, and total cost. Filter by user_id, session_id, or search by trace_id.

​
Trace detail

Opening a trace shows:
  • Span waterfall — the spans laid out by time, so you can see planning, retrieval, tool calls and generations in sequence.
  • Per-span detail — model, token breakdown (input / output / cache), cost, latency, status, and the input/output payloads.
  • Scores — any eval or annotation scores attached to the trace.

​
Where traces come from

Anything that exports to the OTLP endpoint:
Turn a real trace into a regression case by adding it to a dataset.