Telemetry export through a proxy gets its own connections and timeouts
Through 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
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
TelemetryArea: what it touches
ImprovementsKind: in v2.1.317,
ImprovementsSection of the release
What
Claude 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.
The time allowed to open that connection now comes from these settings:
It is 10 seconds if nothing is set, and never more than 30 seconds.
Why
This matters if you export telemetry through a corporate proxy. It only applies when a proxy is configured.
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeFixed OpenTelemetry exports hanging indefinitely behind a proxy that never answers; they now time out after 10 seconds, or…
