Export traces

After this page you can download the traces a filter finds — one row per trace or every span — with their scores, and you know the cap that applies.

Export opens over the trace list with the current filter set. Choose the scope (current filters or selected rows), the shape (one row per trace, or every span), the format (CSV, JSON, or JSONL in the dataset shape) and whether to include scores and labels. The dialog states the cap before you click: at most 5,000 traces. A progress bar counts traces and spans as they arrive; Download names the file from the active view or filters.

• The export read returns spans as JSON; the CSV and per-trace shapes are built in the browser, which is why very large exports are capped.
• Scores and labels are merged from the control plane during the export.
• Nothing is stored server-side: there is no export history, and repeating an export means re-running the same filter.
• To keep traces as regression rows rather than a file, use Add to dataset — see Build a dataset from traces.