Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Investigate a failing trace

Guide — investigate a failing trace.

  1. Open the trace in Premium → Traces

  2. Read the span tree top-down — first failure span is your starting point

  3. Inspect inputs and outputs at every span boundary

  4. Check span-level errors, latencies, costs for outliers

  5. Run an ad-hoc judge against a single span to test hypotheses

See also

PreviousBuild a trace set for agentic evalsNextSchedule continuous trace evaluation

Last updated

Was this helpful?