{"version":"2.1.307","anchor":"otlp-exporters-can-strip-header-env-vars-during-construction","canonical_anchor":"otlp-exporters-can-strip-header-env-vars-during-construction","heading":"Telemetry exporters can ignore header environment variables","tier":"use","area":"Telemetry","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/otlp-exporters-can-strip-header-env-vars-during-construction","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Telemetry exporters can ignore header environment variables\n\nTelemetry exporters can now ignore OTEL_EXPORTER_OTLP_HEADERS and use only the headers given in configuration\n\n**Unclear.** It is not clear when the exporters are set to use only configured headers, or whether that is the default.\n\n**What**\n\nClaude Code can send logs and traces to an OpenTelemetry collector, a service that gathers usage and performance data. Headers, such as a login token, are sent with that data.\n\nWhen the logs or traces exporter is set to use only configured headers, Claude Code now briefly unsets `OTEL_EXPORTER_OTLP_HEADERS` and the matching per-signal headers variable while the exporter is set up. It puts them back when the exporter shuts down. Only the headers given in configuration are then used.\n\n**Why**\n\nThis changes which login headers telemetry sends when headers come from configuration. Headers set in those environment variables are not used by an exporter set up this way.\n\n- Area: Telemetry\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}