Export data

Export data downloads the results of an Explore V2 query as a CSV, TSV, or JSON file. The same export drawer is available from every grid in Explore V2 — the Logs and Spans tabs, the Traces and Templates tabs, and the Overview tab that renders aggregated rows when your query includes a Group By — so you can share investigation results outside Coralogix, run analysis in spreadsheets or notebooks, feed downstream tooling that consumes JSON, archive a snapshot for compliance, or hand off samples to teammates without a Coralogix login.

Choose a data-selection mode

Choose based on how you plan to use the file:

• Pick Grid columns when you want a clean CSV, TSV, or JSON file shaped by what's visible on screen. Each grid column becomes a column (CSV/TSV) or a top-level key (JSON) in the file.
• Pick All logs (or All spans when exporting from the Spans tab) when you need every field per record for analysis, archival, or downstream tooling. The file is denser and not optimized for spreadsheets — JSON is the most natural format here.

If in doubt, Grid columns is the safer default.

Where to export from

The Logs and Spans exports run against the backend, so they include every matching record up to the export cap regardless of grid paging. The Traces, Templates, and Overview exports run client-side and include only the rows already loaded into the grid — scroll or load more before exporting if you need additional rows.

Export from the Overview tab

The Overview tab opens whenever your query produces grouped or aggregated results — that is, when the query includes:

• An aggregation (for example, count, sum, avg).
• A grouping (a Group by clause in Builder mode, or a groupby operator in DataPrime mode).
• Both an aggregation and a grouping.

The Overview tab renders the resulting rows in a grid, and the Export button at the top of that grid downloads those rows. The export reflects the grid exactly as displayed — column names and values match what you see on screen — not the raw underlying events that produced the aggregation.

Available formats on the Overview tab depend on the query language:

• In Builder mode, export aggregated results as CSV or TSV. JSON is not available.
• In DataPrime mode, export aggregated results as CSV, TSV, or JSON.

How to export

1. Run a query in Explore V2 so the grid contains the logs or spans you want.
2. Open Export from the right corner.
3. Choose a data-selection mode (Grid columns or All logs / All spans).
4. Choose a format: CSV, TSV, or JSON.
5. Adjust the row count if needed. Default and cap are both 10,000.
6. Select Export. The file downloads to your browser.

Default columns differ by tab:

• The Logs tab defaults to exporting Timestamp, Source, Application, and Subsystem.
• The Spans tab defaults to exporting Timestamp, Service name, Operation, Duration, and Span ID.

Add or remove columns under Columns to export before you export.

The dialog suggests a default file name. To customize it, enter letters, numbers, and ., _, or - only — up to 255 characters. Other characters show the error Only letters, numbers, and the characters . _ - are allowed and the Export button stays inactive until you fix the name.

How exported data maps to the grid

Most columns in the grid map directly to a single backend field, and they appear in the export with the same name and value. A few columns are different.

Virtual columns

A small number of columns are built in the UI from several raw fields, with fallbacks and normalization across SDKs and sources. They are not stored as a single field on the backend, so they are not included in the export.

Surface	Virtual column	Source fields
Logs	content	message, log, body, event, and similar fields
Spans	resource	Resource attributes (varies by SDK and instrumentation)
Spans	status_code	http.status_code, rpc.grpc.status_code, and semantic-convention equivalents
Spans	span_kind	SERVER, CLIENT, PRODUCER, CONSUMER, INTERNAL (derived from span.kind)

If you add a virtual column under Columns to export, the file will not contain a column with that name. The Spans tab export drawer also shows an inline note: "Span kind, Resource and Status are not supported yet, as they are virtual fields." To capture the same information:

• Pick All logs or All spans to export every raw field, then derive the equivalent column yourself in your spreadsheet or notebook.
• Or select the underlying source fields directly in Columns to export before exporting.

Limitations

Troubleshoot

Learn more

• Logs in Explore V2
• Logs grid
• Explore actions

Support

Reach the Coralogix customer success team 24/7 via in-app chat or by email at support@coralogix.com.

Next steps

Build sharable deep links to Explore V2 with the Copy URL action in Explore actions.