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 the Logs tab and from the Spans tab — use it to 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.
How to export
- Run a query in Explore V2 so the grid contains the logs or spans you want.
- Open Export from the right corner.
- Choose a data-selection mode (Grid columns or All logs / All spans).
- Choose a format: CSV, TSV, or JSON.
- Adjust the row count if needed. Default and cap are both 10,000.
- Select Export. The file downloads to your browser.
Default columns differ by tab:
- The Logs tab defaults to exporting
Timestamp,Source,Application, andSubsystem. - The Spans tab defaults to exporting
Timestamp,Service name,Operation,Duration, andSpan ID.
Add or remove columns under Columns to export before you export.
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
| Area | Limit |
|---|---|
| Maximum rows per export | 10,000 |
| Supported formats | CSV, TSV, and JSON. JSONL and Parquet are not supported. |
| Delivery | Direct browser download only. No email, S3, or background delivery. |
| Execution | Synchronous only. Closing the dialog or navigating away cancels the export. |
| API and Terraform | Not available. Export is UI-only. |
| Scheduling | Not available. Each export must be triggered manually. |
| Truncation | If the query returns more than 10,000 rows, only the first 10,000 are included. There is no warning beyond the row-count cap shown in the dialog. |
| Datasets | Logs and spans. Metrics are not supported. |
| Virtual columns | Span kind, Resource, and Status are not supported in spans exports — they are derived in the UI rather than stored as backend fields. |
Troubleshoot
| Problem | Cause | Resolution |
|---|---|---|
| File contains fewer rows than expected | The query returned more than 10,000 rows and the export was capped. | Refine the query or shorten the time range to fit within 10,000 rows, or run multiple exports across smaller windows. |
| Column shown in the grid is missing from the file | The column is a virtual column built by the UI (for example, content for logs or resource, status_code, and span_kind for spans). It does not exist as a single backend field. | Pick All logs or All spans to export every raw field, or select the underlying source fields explicitly in Columns to export. |
| Spreadsheet shows JSON in cells | All logs or All spans was selected with a CSV or TSV format, so nested objects are serialized into cells. | Re-export with Grid columns, or switch the format to JSON if you want the nested structure preserved. |
| Special characters break the spreadsheet layout | The data contains commas that conflict with the CSV separator. | Re-export with TSV. |
| Export is empty | The query returned no results. | Adjust the query, filters, or time range so the grid shows results before exporting. |
| Browser download is interrupted | The dialog was closed or the page navigated away during export. | Stay on the dialog until the file finishes downloading. |
Learn more
Support
Reach the Coralogix customer success team 24/7 via in-app chat or by email at [email protected].
Next steps
Build sharable deep links to Explore V2 with the Copy URL action in Explore actions.