{"version":"2.1.323","anchor":"otlp-telemetry-endpoint-and-protocol-resolution-connection","canonical_anchor":"otlp-telemetry-endpoint-and-protocol-resolution-connection","heading":"OpenTelemetry export now gives a clear error when protocol and endpoint are missing","tier":"notice","area":"Telemetry","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/otlp-telemetry-endpoint-and-protocol-resolution-connection","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### OpenTelemetry export now gives a clear error when protocol and endpoint are missing\n\nIf no OTLP protocol is set and the endpoint is missing or invalid, Claude Code's telemetry export now stops with a clear error\n\n**Unclear.** It is not clear whether a default protocol is used when the endpoint is valid but no protocol is set.\n\n**What**\n\nClaude Code can send its metrics and logs to your own monitoring system using OpenTelemetry (OTLP, a standard format for this data). It now works out which transport protocol to use in one place.\n\n- If no protocol is set and `OTEL_EXPORTER_OTLP_ENDPOINT` is missing or not a valid address, Claude Code stops with an error that says so. Before, it only gave a generic \"unknown protocol\" error. Protocols are set with the `OTEL_EXPORTER_OTLP_*_PROTOCOL` variables.\n\n- The endpoint address written to logs is cleaned of sensitive parts.\n\n- Reports about failed exports now say whether a network connection was reused, how long it had been idle, and how long Claude Code waited, and repeated errors are counted.\n\n**Why**\n\nA broken monitoring setup now tells you what to fix. If you use an HTTP exporter without setting a protocol, check that exports still arrive, since that case may behave differently now.\n\n- Area: Telemetry\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}