Last updated: August 7, 2026
Log 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.log.ai.attributes_inferred: When true, the dash0.log.attribute.* attributes on this log record were
extracted automatically by the AI-powered log parser.
See AI log patterns.
[3] dash0.log.ai.message_inferred: When true, dash0.log.message was extracted from the raw log body by the
AI-powered log parser rather than taken verbatim.
See AI log patterns.
[4] dash0.log.ai.severity_inferred: When true, the OTel severity number on this log record was inferred from the
log content rather than provided by the instrumentation.
See AI log patterns.
[5] dash0.log.message: Set by the Dash0 log parser. May differ from the raw log body when AI-based
message extraction is applied (indicated by dash0.log.ai.message_inferred).
See AI log patterns.
[6] dash0.log.pattern: Assigned by the Dash0 log grouping processor when a log record matches a known
pattern template. Useful for filtering and grouping recurring log messages.
See AI log patterns.
[7] dash0.monitoring.telemetry_collection_issue: When true, the log message points to a possible problem in the telemetry collection.
Examples include:
- the Dash0 operator cannot instrument a workload for telemetry collection
- the Dash0 operator reports an issue setting up the OpenTelemetry collectors
[8] 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".
[9] 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.
[10] 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.
[11] dash0.operator.version: The collectors managed by the Dash0 Kubernetes operator add this resource attribute to all telemetry.
[12] 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.
[13] 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.
[14] 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.
[15] 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.
[16] dash0.span_event.converted: When true, this log record was created by the Dash0 ingestion pipeline from
a span event.
The resulting log record carries the correct trace context so it correlates with
the original span.
This conversion is an opt-in, per-dataset setting that helps with the transition away from span events, which OpenTelemetry is deprecating in favour of log records linked with trace context.
See Span event to log record conversion.
[17] otel.event.name: This attribute SHOULD be used by non-OTLP exporters when destination does not support EventName or equivalent field. This attribute MAY be used by applications using existing logging libraries so that it can be used to set the EventName field by Collector or SDK components.
[18] otel.log.severity.number: Maps to severity ranges: 1-4 TRACE, 5-8 DEBUG, 9-12 INFO,
13-16 WARN, 17-20 ERROR, 21-24 FATAL.
[19] otel.log.severity.range: Computed by Dash0 from otel.log.severity.number. Useful for
filtering and grouping logs by broad severity level.