{"version":"2.1.288","anchor":"datadog-log-flush-hardening-and-gzip-state","canonical_anchor":"datadog-log-flush-hardening-and-gzip-state","heading":"Sending Claude Code's diagnostic logs no longer fails on an error","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/datadog-log-flush-hardening-and-gzip-state","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Sending Claude Code's diagnostic logs no longer fails on an error\n\nAn error while sending diagnostic logs to Datadog is now caught and logged, and the sender tracks whether compression has been tried\n\n**Unclear.** How the gzip compression path is used is not known.\n\n**What**\n\nWhen Claude Code sends its diagnostic logs to Datadog, an error during sending is now caught and noted in the log instead of left to propagate. The sender also keeps track of whether gzip compression has been tried yet.\n\n**Why**\n\nThis is a reliability change to Claude Code's own usage reporting.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}