{"version":"2.1.275","anchor":"otel-custom-header-helper-now-prefetched-for-http-based-expo","canonical_anchor":"new-telemetry-gate-for-opentelemetry-header-helper-failures","heading":"OpenTelemetry header helper: prefetching and failure warnings","tier":"notice","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/otel-custom-header-helper-now-prefetched-for-http-based-expo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### OpenTelemetry header helper: prefetching and failure warnings\n\nClaude Code now prefetches your custom OpenTelemetry header helper for HTTP exporters and warns you if it fails\n\n**What**\n\n- For OpenTelemetry (OTel, a standard for exporting telemetry data) exporters using HTTP-based protocols (`http\/json` or `http\/protobuf`), a user-configured `otelHeadersHelper` is now prefetched once per process to prime its cache, instead of being fetched lazily on the first request.\n\n- If `otelHeadersHelper` fails, Claude Code now shows a dismissible warning notification (visible for 30 seconds) telling you that telemetry is not being exported and to check `\/status` for details.\n\n**Why**\n\nPrefetching avoids a delay on the first telemetry request, and the new warning makes it clear when your custom header helper is broken instead of silently dropping telemetry exports.\n\n- Area: Telemetry\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}