Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Agent ProxyArea: what it touches
Internal ChangesKind: in v2.1.265,
Internal ChangesSection of the release
Unclear What triggers or consumes a connection's bad-event budget, and what happens when it's exhausted, isn't specified.
What
The 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.
When 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.
Why
This keeps a single misbehaving or noisy connection from flooding logs with repeated identical bad-event messages, while still surfacing how many events were suppressed.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat triggers or consumes a connection's bad-event budget, and what happens when it's exhausted, isn't specified.
