Unclear Which specific problems the check reports is not stated.
What
In a self-hosted gateway's configuration, each telemetry.forward_to entry says where to send telemetry (usage and performance data). Entries that include auth login settings are now checked when the configuration is loaded, and any problems are reported against that entry's Google login settings.
Why
If you run your own gateway, mistakes in telemetry forwarding login settings show up when the configuration is checked, rather than later.
Names in the bundletelemetry.forward_to
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 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-gateway see the edit
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
Which specific problems the check reports is not stated.
Anthropic's documentation agrees
Anthropic's documentation has since written up telemetry.forward_to, on Claude apps gateway for Amazon Bedrock, Claude Platform on AWS…
Anthropic's release notes agree
Added auth: { google: {} } for Claude apps gateway telemetry.forward_to destinations, so telemetry can be exported straight to Google…