{"version":"2.1.310","anchor":"otlp-exporter-http-agent-takes-carriesourtoken-option","canonical_anchor":"otlp-exporter-http-agent-takes-carriesourtoken-option","heading":"Telemetry export to your own collector uses separate certificate and proxy settings","tier":"notice","area":"Telemetry","scope":"org","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/otlp-exporter-http-agent-takes-carriesourtoken-option","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Telemetry export to your own collector uses separate certificate and proxy settings\n\nWhen sending OpenTelemetry data, Claude Code now builds its connection from your own certificate and proxy settings, not the shared setup\n\n**Unclear.** It is not clear which of your certificate and proxy settings now apply to the telemetry connection, or when the strict connection is chosen.\n\n**What**\n\nClaude Code can send usage data to a collector you run, using OpenTelemetry (a common standard for sending this kind of data, also called OTLP). Before, every connection Claude Code made used the same rules for which certificates to trust and which proxy to go through. A proxy is a server that relays network traffic. Connections for this telemetry export now take a separate path. Claude Code checks your own certificate authority and proxy settings and builds either a \"customer\" or a \"strict\" connection from them.\n\n**Why**\n\nThis changes which certificates and proxy are used when Claude Code reaches your collector. If you send telemetry through a corporate proxy or a custom certificate, check that it still arrives.\n\n- Area: Telemetry\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: yes"}