OTEL_EXPORTER_OTLP_LOGS_TIMEOUT
A Claude Code environment variable, read out of the shipped bundle. It has been in the build since v2.1.317, including the newest one read.
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
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.317.
In the changelogs
1Releases whose published page names OTEL_EXPORTER_OTLP_LOGS_TIMEOUT.
-
v2.1.317
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
found in this entry's text
First cited
1The earliest release whose published evidence quoted OTEL_EXPORTER_OTLP_LOGS_TIMEOUT was v2.1.317, 2 Nov 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.
Presence across releases
1Build by build
2One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the environment variable does. All environment variables.