{"version":"2.1.317","anchor":"otlp-proxy-tunnel-agent-and-timeouts","canonical_anchor":"otlp-proxy-tunnel-agent-and-timeouts","heading":"Telemetry export through a proxy gets its own connections and timeouts","tier":"notice","area":"Telemetry","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/otlp-proxy-tunnel-agent-and-timeouts","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Telemetry export through a proxy gets its own connections and timeouts\n\nThrough a proxy, OpenTelemetry exports now get their own connection per protocol, with a timeout from the OTLP settings, 10s by default and 30s at most\n\n**What**\n\nClaude Code can send telemetry (usage and performance data) to your own monitoring system using OpenTelemetry, an open standard for that kind of data. When that traffic goes through a proxy, each export protocol now gets its own dedicated connection through the proxy. Before, they all shared a single proxy connection.\n\nThe time allowed to open that connection now comes from these settings:\n\n- `OTEL_EXPORTER_OTLP_TIMEOUT` for all telemetry\n\n- `OTEL_EXPORTER_OTLP_LOGS_TIMEOUT` and the matching per-signal settings for metrics and traces\n\nIt is 10 seconds if nothing is set, and never more than 30 seconds.\n\n**Why**\n\nThis matters if you export telemetry through a corporate proxy. It only applies when a proxy is configured.\n\n- Area: Telemetry\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}