Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.281 ·

New otlp_export health telemetry for customer OpenTelemetry exporters

Claude Code now records whether its OpenTelemetry exports to your own collector succeed or fail, with an error code on failure

Entry
JSON All of v2.1.281
EntryKind: in v2.1.281,
ChangesSection of the release
What

OpenTelemetry (OTLP) is a standard way to send metrics, logs and traces to a monitoring system you run yourself. When you set this up, Claude Code now records an otlp_export event about how those exports went:

  • The first successful export of each kind (metrics, logs or traces) records one success event.
  • Each distinct failure records one failure event with an error code. Codes include grpc_N, http_401, http_403, http_Nxx, "timeout", "http_retries_exhausted", headers_helper_*, SSL codes or "other".
  • Failure events also record the protocol, the HTTP status and whether a proxy was used.

Console and Prometheus exporters are not tracked. Traces are also not tracked when the traces endpoint matches an internal check. The debug line printed on the first export is unchanged.

Why

Problems with your telemetry setup now leave a record with a specific reason, such as a rejected login or a timeout.

See this entry in the whole of v2.1.281 →

Feedback