What
The gateway configuration has a new key, telemetry.resource_attributes. These are labels that get attached to the telemetry (usage and performance data) that sessions send. What happens depends on telemetry.forward_to:
telemetry.forward_toset: the labels are handed to each session the gateway starts, asOTEL_RESOURCE_ATTRIBUTESand asotlpResourceAttributes.telemetry.forward_toempty: the gateway warns that the labels are not applied.
Why
You can tag all telemetry from gateway-started sessions with your own labels. They only take effect when forwarding is configured, and the warning tells you when they are being ignored.
Names in the bundletelemetry.resource_attributestelemetry.forward_to
Documented inclaude-code/claude-apps-gateway
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.
Sessions get the labels only when you also set `telemetry.forward_to` and `listen.public_url`. This example adds two labels:claude-apps-gateway-config see the edit
Confirmed since
Anthropic's documentation has since written up telemetry.resource_attributes, on Claude apps gateway configuration.
To put fixed labels such as `service.namespace` or `deployment.environment.name` on the telemetry of sessions signed in through the gateway, set `telemetry.resource_attributes`. Each label is an OpenTelemetry resource attribute, and every …claude-apps-gateway-config see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up telemetry.resource_attributes, on Claude apps gateway configuration.
Anthropic's release notes agree
Added telemetry.resource_attributes to the Claude apps gateway config, to put fixed labels on the telemetry of Claude Desktop and /login…