{"version":"2.1.232","anchor":"policy-limits-fetch-telemetry-gains-auth-shape-and-error-fie","canonical_anchor":"policy-limits-fetch-telemetry-gains-auth-shape-and-error-fie","heading":"Policy-limits fetch telemetry gains auth-shape and error fields","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/policy-limits-fetch-telemetry-gains-auth-shape-and-error-fie","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Policy-limits fetch telemetry gains auth-shape and error fields\n\nPolicy limit fetch events now record how you authenticated and why the server said no.\n\n**What**\n\nThe `tengu_policy_limits_fetch` event now records how the request was authenticated and why the server rejected it.\n\n**Details**\n\n- Added: `has_custom_base_url`, `has_auth_token`, `has_api_key_helper`, `api_key_prefix`.\n- Added `server_error_type` and `server_error_code` from the response body, collapsed to `other` unless on a fixed allow-list such as `rate_limit_error` or `ip_not_in_allowed_range`.\n\n**Evidence**\n\n`server_error_type`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}