Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.307entry #236

Claude Code v2.1.307 ·

OpenTelemetry metrics export is set up a little differently

When metrics are sent over OpenTelemetry by gRPC or HTTP protobuf, Claude Code now prepares an extra resource before creating the exporter

Under the hood Internal Changes
JSON All of v2.1.307
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.307,
Internal ChangesSection of the release

Unclear It is not known what the extra step does or whether exported metrics look any different.

What

OpenTelemetry is a standard for sending usage metrics to a monitoring system you run. Claude Code can export metrics this way using the protocol you choose with OTEL_EXPORTER_OTLP_METRICS_PROTOCOL. For both grpc and http/protobuf, it now prepares an extra resource before it creates the exporter.

Why

This may change how metrics export is set up.

Read from
Names in the bundleOTEL_EXPORTER_OTLP_METRICS_PROTOCOL
What the documentation says
Documented inclaude-code/monitoring-usage
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 doubtIt is not known what the extra step does or whether exported metrics look any different.

See this entry in the whole of v2.1.307 →

Feedback