Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
TelemetryArea: what it touches
Internal ChangesKind: in v2.1.281,
Internal ChangesSection of the release
Unclear The finding does not say what the per-export callback does with each result.
What
Claude Code can send traces to a telemetry service you choose, using OpenTelemetry (OTLP). A trace is a timed record of the steps in a piece of work. The service address comes from the environment variable OTEL_EXPORTER_OTLP_TRACES_ENDPOINT.
A new check looks at that address. If it matches an address known when Claude Code started and its path is for traces, it counts as the startup gateway. In every other case, Claude Code now records which protocol is used and whether the export goes through a proxy ({protocol, viaProxy}), and calls a result callback after each export.
The "[3P telemetry] First ... export" debug message is unchanged.
Why
If you send traces to your own telemetry service, Claude Code now tracks how each export went. When traces go to the startup gateway, this extra tracking is skipped.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed sinceAnthropic's documentation has since written up OTEL_EXPORTER_OTLP_TRACES_ENDPOINT, on Monitoring.| `OTEL_EXPORTER_OTLP_TRACES_ENDPOINT` | OTLP traces endpoint, overrides `OTEL_EXPORTER_OTLP_ENDPOINT` | `http://localhost:4318/v1/traces` |monitoring-usagesee the edit
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding does not say what the per-export callback does with each result.
Anthropic's documentation agreesAnthropic's documentation has since written up OTEL_EXPORTER_OTLP_TRACES_ENDPOINT, on Monitoring.
