{"version":"2.1.290","anchor":"datadog-log-posting-backs-off-when-an-egress-proxy-refuses-t","canonical_anchor":"datadog-log-posting-backs-off-when-an-egress-proxy-refuses-t","heading":"Claude Code stops trying to send logs when a network proxy blocks them","tier":"internal","area":"Telemetry","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/datadog-log-posting-backs-off-when-an-egress-proxy-refuses-t","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Claude Code stops trying to send logs when a network proxy blocks them\n\nWhen a network proxy refuses Datadog's address, Claude Code pauses sending logs there for a while and drops them instead of retrying\n\n**What**\n\nClaude Code sends some logs to Datadog, an outside logging service. On networks where an egress proxy (a gateway that controls which outside addresses programs may reach) refuses Datadog's address, Claude Code now stops sending logs for a cool-off period and drops them during it. Before, every failure was retried at later sends.\n\nA failure to compress the logs is now reported only after a later send succeeds, instead of straight away.\n\n**Why**\n\nOn locked-down networks this cuts out a stream of requests that were always going to fail.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}