Log Records Download Request
Definition
Request for the LogRecordsDownload API. Accepts the same query as GetLogRecords
(filter, timeRange, dataset, ordering) and returns the matching records
serialized as a downloadable file rather than as a JSON page.
The response is streamed, so the export is not paginated: a single request returns up
to limit records, capped at 5000. Adaptive sampling is always disabled for exports,
so an exported file is never a sample.
A range of time between two time references.
Optional dataset to query across. Defaults to whatever is configured to be the default dataset for the organization.
The ordering criteria for the exported logs. Records are written to the file in
this order.
Supported ordering key: otel.log.time (log timestamp, defaults to descending)
The serialization format of the exported file.
txt: One rendered log line per record, carrying a fixed field set of timestamp, severity, resource, body and trace ID. Ignorescolumns.ndjson: One OTLP JSON payload per line, each carrying a single log record inside the sameresourceLogsenvelopeGetLogRecordsreturns, so each line is independently parseable by any OTLP JSON consumer.yaml: The same per-record OTLP payloads asndjson, as a multi-document YAML stream with documents separated by---.csv: A header row plus one row per record, flattened to the requestedcolumns.
"txt""ndjson""yaml""csv"The maximum number of log records to export. Defaults to, and is capped at, 5000.
A larger value is rejected rather than silently clamped. Use the Dash0 CLI
(dash0 logs query) to export volumes beyond this cap.
Attribute keys to emit as columns, in order, for the csv format — resource,
scope, or log record attributes (e.g. service.name, otel.log.body). Ignored by
the other formats, which have a fixed field set.
Used by 1
These schemas and endpoints reference this type directly.