Exports

Estimated reading: 3 minutes

The Exports page provides a centralized view of all export requests generated across the Control Plane. Exports allow users to download large datasets from supported pages in the desired file format.

Export requests are processed asynchronously so that ongoing work is not interrupted. Once an export is complete, an email notification is sent to the user who initiated the request. The download link generated for the export remains valid for one hour after completion.

Exports are typically used when large volumes of data need to be extracted for reporting, analysis, auditing, troubleshooting, or sharing outside the platform. Export requests can be initiated from supported pages, such as the Tracing page, by selecting records and exporting them in a supported file format.

Role-Based Permissions

The available export operations depend on the user's project role.

Role	Permissions
Owner	Can create, manage, and download exports based on access to the underlying project data.
Admin	Can create, manage, and download exports based on access to the underlying project data.
Member	Can create, manage, and download exports based on access to the underlying project data.
Viewer	Can view export records but cannot create, modify, or download exports.

How to Request an Export

You can request an export from any supported page in the Control Plane that offers export functionality, such as the Tracing page. The steps below walk through requesting an export using the Tracing page as an example.

1. Navigate to the Tracing page.
2. Select the traces you want to export. You can select individual traces or use filters to narrow down the dataset before selecting.
3. Click Export.
4. Choose the desired file format for the export: CSV, JSON, or JSONL.
5. Confirm the export request.

Once submitted, the export request is added to the Exports list with a status of Queued. From here, it moves through the following states:

a. Queued: The request is waiting to be processed. You can cancel the export at this stage using the Actions column.
b. Completed: The export finished successfully. A Download URL is generated and remains valid for one hour. You will receive an email when the export is ready.
c. Failed: The export could not be completed. No actions are available for a failed export; you must submit a new export request.

Notes:

If the download link expires before you access it, you must submit a new export request, as expired links cannot be reactivated.
Filters on trace-level columns (Trace Name, Trace Tags, User ID, and Trace Environment) and Comments are not included in observation exports. As a result, the exported data may contain more records than expected.

Export Scope Limitations

Exports only apply filters relevant to the record type being exported.

a. Trace exports apply trace-level filters only (for example, Trace Name, Trace Tags, User ID, Trace Environment). Observation-level filters (Level, Tokens, Cost, Latency) and Comments filters are not applied.

b. Observation exports apply observation-level filters only (Level, Tokens, Cost, Latency). Trace-level filters (Trace Name, Trace Tags, User ID, Trace Environment) and Comments filters are not applied.

Note: If the exported file contains more data than expected, verify whether unsupported filters were applied.

Exports

Role-Based Permissions

How to Request an Export

Export Scope Limitations

Exports

CONTENTS