What probably matters to youSection of the release
What
The gateway can forward telemetry (usage and performance data in the OpenTelemetry, or OTel, format) to other services listed under telemetry.forward_to. Those destinations used to send only fixed headers you wrote yourself.
When it is set, the exporter fetches Google access headers, caches them per destination, removes any Authorization header and adds the Google ones before sending. Other headers you set are kept.
auth.google requires an https googleapis.com URL and no Authorization header of your own.
You can send gateway telemetry straight to Google Cloud collectors without making tokens by hand or writing a helper for headers. The model list change lets gateway users see which models offer the 1M context window.
Read from
Names in the bundleauth.google.service_account_jsontelemetry.forward_to
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 sinceAnthropic's documentation has since written up telemetry.forward_to, on Claude apps gateway for Amazon Bedrock, Claude Platform on AWS, Google Cloud, and Microsoft Foundry.* **Telemetry destination**: in sessions signed in through `/login`, the CLI sends its OTLP/HTTP exports to the gateway rather than to a locally set `OTEL_EXPORTER_OTLP_ENDPOINT`, unless a policy [names your collector as the endpoint](http…claude-apps-gatewaysee the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up telemetry.forward_to, on Claude apps gateway for Amazon Bedrock, Claude Platform on AWS…
Anthropic's release notes agreeAdded auth: { google: {} } for Claude apps gateway telemetry.forward_to destinations, so telemetry can be exported straight to Google…
