Export traces

Select rows in the trace list, click Export in the selection bar, and choose Summaries as CSV or Summaries as JSON. The browser builds the file from the selected rows and names it traces-<time>.csv or traces-<time>.json.

Each row is one trace summary. The CSV columns are traceId, startTime, operation, serviceName, status, model, provider, latencyMs, tokensIn, tokensOut, spanCount, sessionId and userId. Scores, labels and spans are not included.

To export spans, use the Legacy dashboard, opened from Legacy dashboard in the user menu. Its export downloads the summaries of the filtered list, or all their spans as JSON or CSV. The spans arrive as JSON and the browser builds the CSV, which is why one export is capped at 5,000 traces.

• Nothing is stored server-side. There is no export history, and repeating an export means selecting or filtering again.
• To keep traces as regression rows in place of a file, use Add to dataset. See Build a dataset from traces.