Last updated: August 7, 2026
Span Attributes
Attributes:
[1] dash0.auth.token: Set at ingestion time by the Dash0 backend.
Useful for identifying which token was used when multiple authentication tokens are in use.
[2] dash0.operation.name: Derived at ingestion time from span attributes using pattern templates defined by
operation naming rules
(e.g., GET /api/users for HTTP, SELECT ... FROM my-table for database).
Cardinality reduction is applied automatically.
Can be overridden by setting the attribute before telemetry reaches Dash0.
[3] dash0.operation.type: Determined at ingestion time by evaluating span attributes against a prioritised
set of operation naming rules.
Cannot be overridden by users; Dash0 always computes it from the span data.
[4] dash0.operator.collector_managed_by: The collectors managed by the Dash0 Kubernetes operator add this resource attribute to all telemetry.
If set, the value is always "dash0-operator".
[5] dash0.operator.collector_role: The Dash0 Kubernetes operator manages two types of OpenTelemetry collectors, a DaemonSet for node-local telemetry and
a Deployment for collecting Kubernetes events and cluster-wide metrics.
This attribute shows which collector type collected a particular telemetry signal.
If set, the value is either "daemonset" or "deployment".
Coalesced resources might combine telemetry from the DaemonSet collector as well as the Deployment collector, hence they
might have both values.
[6] dash0.operator.uid: The collectors managed by the Dash0 Kubernetes operator add this resource attribute to all telemetry.
It is stable across the life-time of the cluster.
[7] dash0.operator.version: The collectors managed by the Dash0 Kubernetes operator add this resource attribute to all telemetry.
[8] dash0.resource.hash: Computed at ingestion time by hashing all resource attributes in a deterministic
(sorted) order. It is the most fine-grained resource identifier: each unique set of
resource attributes produces a different hash.
See resource equality
for how dash0.resource.hash relates to dash0.resource.id.
[9] dash0.resource.id: Computed at ingestion time by applying resource equality rules.
Two telemetry items with the same dash0.resource.id are considered to originate
from the same logical resource, even if their full attribute sets differ.
[10] dash0.resource.name: Derived at ingestion time from resource attributes using a precedence hierarchy
(e.g., Kubernetes pod name, container name, service name). Can be overridden by
setting the attribute before telemetry reaches Dash0.
See identify resources by name and type.
[11] dash0.resource.type: Assigned at ingestion time based on the presence of technology-specific resource
attributes. For example, the presence of k8s.pod.uid results in type k8s.pod.
See identify resources by name and type.
[12] dash0.span.name: Computed at ingestion time from span attributes using the same
operation naming rules
that drive dash0.operation.name. While dash0.operation.name identifies the
logical operation, dash0.span.name is the per-span normalised name with
cardinality reduction applied (e.g., path parameters replaced with :id).
[13] dash0.span.type: Assigned at ingestion time using the same rule evaluation that produces
dash0.operation.type. Values are normalised to lowercase.
[14] dash0.trace.origin.synthetic_check.attempt_id: Extracted from bytes 12–16 of the trace ID for synthetic-check traces.
Only set when dash0.trace.origin.type is SYNTHETIC_CHECK.
[15] dash0.trace.origin.synthetic_check.check_id: Extracted from bytes 6–12 of the trace ID for synthetic-check traces (prefix d0synt).
Only set when dash0.trace.origin.type is SYNTHETIC_CHECK.
[16] dash0.trace.origin.synthetic_check.follow_redirect: Extracted from byte 7 of the parent span ID on server root spans of synthetic-check traces.
Only set when dash0.trace.origin.type is SYNTHETIC_CHECK and the span matches the
synthetic-check client span pattern.
[17] dash0.trace.origin.type: Determined at ingestion time by inspecting well-known prefixes in the trace ID.
Traces whose ID starts with d042 are classified as WEB (browser/RUM).
Traces whose ID starts with d0synt (hex-encoded) are classified as SYNTHETIC_CHECK.
All other traces receive the value UNKNOWN.
[18] dash0.trace.origin.web.event.id: On server root spans of web traces, the parent span ID is removed from the span
and stored as this attribute instead.
Only set when dash0.trace.origin.type is WEB and CRC32 checksum validation of
the trace ID passes.
[19] dash0.trace.origin.web.session.id: Extracted from bytes 3–11 of the trace ID for web traces (prefix d042).
Only set when dash0.trace.origin.type is WEB.