{"version":"2.1.288","anchor":"datadog-log-gzip-with-automatic-fallback","canonical_anchor":"datadog-log-gzip-with-automatic-fallback","heading":"Diagnostic logs sent to Datadog can be compressed, with a fallback","tier":"use","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/datadog-log-gzip-with-automatic-fallback","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Diagnostic logs sent to Datadog can be compressed, with a fallback\n\nLog batches sent to Datadog can now be gzip-compressed, falling back to uncompressed if Datadog refuses one\n\n**Unclear.** Whether compression is on by default when the environment variable is not set is not established.\n\n**What**\n\nClaude Code sends batches of diagnostic logs to Datadog, a logging service. These batches can now be compressed with gzip to make them smaller. Setting `CLAUDE_CODE_GZIP_DATADOG_LOGS` turns compression on or off; without it, Claude Code uses a built-in default.\n\n- If Datadog refuses a compressed batch, Claude Code resends it uncompressed and stops compressing for the rest of that run.\n\n- A \"too many requests\" reply (HTTP 429) does not count as a refusal.\n\n**Why**\n\nThis only affects how internal diagnostic data travels, and nothing changes in what you see.\n\n- Area: Telemetry\n- Names: `CLAUDE_CODE_GZIP_DATADOG_LOGS`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}