Spans Download Request
Definition
Request for the SpansDownload API. Accepts the same query as GetSpans
(filter, timeRange, dataset, ordering) and returns the matching spans
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 spans, capped at 5000. Adaptive sampling is always disabled for exports,
so an exported file is never a sample. Unlike GetSpans this request therefore takes
no sampling, and one sent anyway is ignored: the sampling path can substitute a
duration-percentile filter and quietly change which spans the file contains, so
exports never take it.
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 spans. Spans are written to the file in
this order.
Supported ordering key: otel.span.start_time (span start timestamp, defaults to
descending), optionally followed by otel.trace.id then otel.span.id ascending,
which is the tiebreak span retrieval appends to keep its cursor stable.
The serialization format of the exported file.
txt: One rendered span line per record, carrying a fixed field set of start timestamp, service, span name, duration, kind, status code, trace ID and span ID. Ignorescolumns.ndjson: One OTLP JSON payload per line, each carrying a single span inside the sameresourceSpansenvelopeGetSpansreturns, so each line is independently parseable by any OTLP JSON consumer.yaml: The same per-span OTLP payloads asndjson, as a multi-document YAML stream with documents separated by---.csv: A header row plus one row per span, flattened to the requestedcolumns.
"txt""ndjson""yaml""csv"The maximum number of spans to export. Defaults to, and is capped at, 5000.
A larger value is rejected rather than silently clamped. Use the Dash0 CLI
(dash0 spans query) to export volumes beyond this cap.
Attribute keys to emit as columns, in order, for the csv format — resource,
scope, or span attributes (e.g. service.name, otel.span.duration). Ignored by
the other formats, which have a fixed field set.
Used by 1
These schemas and endpoints reference this type directly.