Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.265 ·

Telemetry relay can forward individual signal types instead of always OTLP for all three

← All of v2.1.265 Home All releases

Telemetry export can now send metrics, logs, and traces to different destinations instead of forcing all three to OTLP

TierUse it nowhow much it should matter to you
Useful3my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaTelemetrywhat it touches
KindImprovementsin v2.1.265,
Use it now Notable

Telemetry export can now send metrics, logs, and traces to different destinations instead of forcing all three to OTLP

What

The OTEL_METRICS_EXPORTER, OTEL_LOGS_EXPORTER, and OTEL_TRACES_EXPORTER environment variables are now each computed individually based on the telemetry.forward_to configuration setting, rather than always being fixed to "otlp" (a standard telemetry export protocol).

Why

This lets you route metrics, logs, and traces to different backends per signal type instead of being forced to send all three the same way, giving more flexible control over where telemetry data ends up.

Read from
Names in the bundleOTEL_METRICS_EXPORTEROTEL_LOGS_EXPORTEROTEL_TRACES_EXPORTERtelemetry.forward_to
What the documentation says
Documented inclaude-code/claude-apps-gateway
Since it was published

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 since Anthropic's documentation has since written up telemetry.forward_to, on Claude apps gateway configuration. | `provider: anthropic` upstreams, Workload Identity Federation token exchange, `telemetry.forward_to` exports | Resolved and checked locally, then `CONNECT` to the checked IP address through the proxy. A telemetry collector listed in `NO_… claude-apps-gateway-config see the edit
Confirmed since Anthropic's documentation has since written up OTEL_TRACES_EXPORTER, on Claude apps gateway configuration. * `OTEL_METRICS_EXPORTER`, `OTEL_LOGS_EXPORTER`, and `OTEL_TRACES_EXPORTER`, each set to `otlp` if at least one `forward_to` destination enables that signal and to `none` otherwise claude-apps-gateway-config see the edit
Confirmed since Anthropic's documentation has since written up OTEL_LOGS_EXPORTER, on Claude apps gateway configuration. * `OTEL_METRICS_EXPORTER`, `OTEL_LOGS_EXPORTER`, and `OTEL_TRACES_EXPORTER`, each set to `otlp` if at least one `forward_to` destination enables that signal and to `none` otherwise claude-apps-gateway-config see the edit
Confirmed since Anthropic's documentation has since written up OTEL_METRICS_EXPORTER, on Claude apps gateway configuration. * `OTEL_METRICS_EXPORTER`, `OTEL_LOGS_EXPORTER`, and `OTEL_TRACES_EXPORTER`, each set to `otlp` if at least one `forward_to` destination enables that signal and to `none` otherwise claude-apps-gateway-config see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up OTEL_METRICS_EXPORTER, on Claude apps gateway configuration.

See this entry in the whole of v2.1.265 →

Feedback