Last updated: August 7, 2026
Metric 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.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".
[3] 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.
[4] 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.
[5] dash0.operator.version: The collectors managed by the Dash0 Kubernetes operator add this resource attribute to all telemetry.
[6] 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.
[7] 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.
[8] 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.
[9] 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.