{"version":"2.1.281","anchor":"request-telemetry-now-tracks-json-and-wire-bytes-and-gzip-fa","canonical_anchor":"request-telemetry-now-tracks-json-and-wire-bytes-and-gzip-fa","heading":"Request telemetry now tracks JSON and wire bytes and gzip fallback","tier":"internal","area":"Telemetry","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/request-telemetry-now-tracks-json-and-wire-bytes-and-gzip-fa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Request telemetry now tracks JSON and wire bytes and gzip fallback\n\nRequest telemetry now records JSON and on-the-wire byte counts plus whether gzip compression was used, skipped or fell back\n\n**Unclear.** The finding does not say what value the timeout helper's (n+30)*1000 is based on.\n\n**What**\n\nTelemetry is the usage and diagnostic data Claude Code reports. For requests, it now adds up and records:\n\n- `json_bytes`: the size of the request data.\n\n- `wire_bytes`: the size actually sent.\n\n- `body_gzip`, `gzip_skip` and `gzip_fallback_status`: whether the request was compressed with gzip, skipped compression, or fell back.\n\nThere is also a new error type that records when a request started (`startedAtMs`), and a new timeout helper.\n\n**Why**\n\nThis is diagnostic data. It does not change what you see.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}