Having good resource attributes on your telemetry is paramount to understanding what is going on in your workloads. Logs, metrics and traces without resource information are basically just data without context. And yet, making sure there are correct Kubernetes resource attributes on all your telemetry is not always easy.
That v0.36 of the Dash0 operator now automatically adds k8s.namespace.name, k8s.pod.name, k8s.pod.uid, and k8s.container.name to all workloads via the Dash0 injector. Under the hood, these attributes are added to the resource attributes sent by your applications via the OTEL_RESOURCE_ATTRIBUTES environment variable. If the workload uses an OpenTelemetry SDK, this environment variable is automatically picked up, and the attributes defined in it are sent along with all the spans, metrics and log records that the application emits.
What's more, the Kubernetes Attributes Processor (which is deployed automatically by the Dash0 operator) will enrich telemetry with a host of other Kubernetes related resource attributes, like the Kubernetes namespace identifier, deployment name and unique identifier, replicaset name and unique identifier etc.
One less thing to worry about, one more thing that just works with Dash0.
