{"version":"2.1.284","anchor":"managed-gateway-config-validates-telemetryforward-to-auth","canonical_anchor":"managed-gateway-config-validates-telemetryforward-to-auth","heading":"Gateway config now checks the login settings for telemetry forwarding","tier":"notice","area":"Gateway","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/managed-gateway-config-validates-telemetryforward-to-auth","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Gateway config now checks the login settings for telemetry forwarding\n\nGateway configuration now checks the `auth` settings on each `telemetry.forward_to` entry and reports problems with their Google login settings\n\n**Unclear.** Which specific problems the check reports is not stated.\n\n**What**\n\nIn 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.\n\n**Why**\n\nIf you run your own gateway, mistakes in telemetry forwarding login settings show up when the configuration is checked, rather than later.\n\n- Area: Gateway\n- Names: `telemetry.forward_to`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}