{"version":"2.1.229","anchor":"opentelemetry-can-be-sent-through-anthropic-s-first-party-ga","canonical_anchor":"opentelemetry-can-be-sent-through-anthropic-s-first-party-ga","heading":"OpenTelemetry can be sent through Anthropic's first-party gateway","tier":"use","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/opentelemetry-can-be-sent-through-anthropic-s-first-party-ga","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### OpenTelemetry can be sent through Anthropic's first-party gateway\n\nTelemetry can route through Anthropic's own gateway, but only under a narrow set of conditions.\n\n**What**\n\nTelemetry export now decides per signal (metrics, logs, traces) whether to send OTLP data to a gateway endpoint derived from `ANTHROPIC_BASE_URL`, authenticated with a `Bearer` header from `ANTHROPIC_AUTH_TOKEN`. It only does this when `CLAUDE_CODE_PROVIDER_MANAGED_BY_HOST` is set, the auth mode is first-party\/gateway, the token is scoped to the gateway audience, you have set no OTLP headers of your own, and your OTLP endpoint already matches the derived URL. Any other combination sends nothing.\n\n**Details**\n\n- The check runs separately for each signal, so metrics can qualify while traces do not.\n- User-set `OTEL_EXPORTER_OTLP_*` headers disqualify the signal outright, so your own collector configuration is never overridden.\n- Falls back to returning \"do not send\" rather than erroring.\n\n**Evidence**\n\n`claude-gateway`\n\n- Area: Telemetry\n- Names: `ANTHROPIC_BASE_URL`, `ANTHROPIC_AUTH_TOKEN`, `CLAUDE_CODE_PROVIDER_MANAGED_BY_HOST`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 4\/5"}