{"version":"2.1.281","anchor":"gateway-new-telemetryresource-attributes-config-key","canonical_anchor":"gateway-new-telemetryresource-attributes-config-key","heading":"gateway: new telemetry.resource_attributes config key","tier":"use","area":"Gateway","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/gateway-new-telemetryresource-attributes-config-key","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### gateway: new telemetry.resource_attributes config key\n\nThe gateway config accepts telemetry.resource_attributes, labels passed to spawned sessions when telemetry.forward_to is set\n\n**What**\n\nThe 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`:\n\n- `telemetry.forward_to` set: the labels are handed to each session the gateway starts, as `OTEL_RESOURCE_ATTRIBUTES` and as `otlpResourceAttributes`.\n\n- `telemetry.forward_to` empty: the gateway warns that the labels are not applied.\n\n**Why**\n\nYou 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.\n\n- Area: Gateway\n- Names: `telemetry.resource_attributes`, `telemetry.forward_to`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5"}