Expert guidance for configuring and deploying the OpenTelemetry Collector. Use when setting up a Collector pipeline, configuring receivers, exporters, or processors, deploying a Collector to Kubernetes or Docker, or forwarding telemetry to Dash0. Triggers on requests involving collector, pipeline, OTLP receiver, exporter, or Dash0 collector setup.
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Use the resource processor (not transform) for static resource attributes.
processors:
resource/static-env:
attributes:
- key: deployment.environment.name
value: production
action: upsert
- key: k8s.cluster.name
value: prod-us-west-2
action: upsertTo copy a resource attribute down to the span or log level, use the transform processor:
processors:
transform/copy-resource:
error_mode: ignore
trace_statements:
- context: span
statements:
- set(span.attributes["deployment.environment.name"], resource.attributes["deployment.environment.name"]) where resource.attributes["deployment.environment.name"] != nil