{"version":"2.1.247","anchor":"compressed-body-fallback-telemetry-names-which-caller-retrie","canonical_anchor":"compressed-body-fallback-telemetry-names-which-caller-retrie","heading":"Compressed-body fallback telemetry names which caller retried","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/compressed-body-fallback-telemetry-names-which-caller-retrie","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Compressed-body fallback telemetry names which caller retried\n\nUncompressed-retry telemetry now names which caller retried the request.\n\n**What**\n\nWhen a gzipped request body is rejected and resent uncompressed, the counter is now `ccr_worker_gzip_request_body` for the CCR worker rollout and `api_gzip_request_body` otherwise, with the rollout label defaulting to \"api\".\n\n**Details**\n\n- The debug line for the fallback now includes `rollout=`.\n- The `tengu_gzip_request_body_fallback` event gained a `rollout` field.\n\n**Evidence**\n\n`ccr_worker_gzip_request_body`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5"}