{"version":"2.1.232","anchor":"policy-limit-telemetry-records-how-you-are-authenticated","canonical_anchor":"policy-limit-telemetry-records-how-you-are-authenticated","heading":"Policy-limit telemetry records how you are authenticated","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/policy-limit-telemetry-records-how-you-are-authenticated","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Policy-limit telemetry records how you are authenticated\n\nPolicy-limit events now describe the shape of your credentials, such as whether a key helper is set.\n\n**What**\n\nThe two events about fetching and caching policy limits now include four extra fields describing the shape of the credentials in use, such as whether an API key helper is configured, alongside the existing token source and fail-closed fields.\n\n**Evidence**\n\n`has_api_key_helper`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}