{"version":"2.1.265","anchor":"agent-proxy-bad-event-telemetry-now-rate-limited-with-suppre","canonical_anchor":"agent-proxy-relay-now-tracks-per-connection-bad-event-budg","heading":"Agent-proxy relay now rate-limits repeated bad-event logging","tier":"internal","area":"Agent Proxy","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/agent-proxy-bad-event-telemetry-now-rate-limited-with-suppre","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Agent-proxy relay now rate-limits repeated bad-event logging\n\nThe agent-proxy relay tracks per-event-type budgets to stop spamming logs with repeated bad-connection events\n\n**What**\n\nThe agent-proxy relay (the component that relays connections for agent sessions) now tracks a `badEventBudgets` map on its connection state, alongside existing counters like `uploadPauses`. A new helper uses a token bucket (a rate-limiting technique that allows bursts up to a limit and refills over time) per event type to suppress repeated identical logging of misbehaving-connection events.\n\nWhen logging resumes after a period of suppression, it now reports a `suppressed_since_last` count so the number of dropped log entries isn't silently lost.\n\n**Why**\n\nThis keeps a single misbehaving or noisy connection from flooding logs with repeated identical bad-event messages, while still surfacing how many events were suppressed.\n\n- Area: Agent Proxy\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}