Merge branch 'topic/christian/gh4318-track-broker-peerings'

* topic/christian/gh4318-track-broker-peerings:
  Use Broker peering directionality when re-peering after backpressure overflows
  Expand Broker APIs to allow tracking directionality of peering establishment
This commit is contained in:
Christian Kreibich 2025-04-21 17:14:44 -07:00
commit ed161692dd
13 changed files with 147 additions and 16 deletions

7
NEWS
View file

@ -124,6 +124,13 @@ Changed Functionality
looking up the "Conn::LOG" identifier allows to directly query the ``EnumVal``
using ``ID::GetVal()``.
- When the send buffer to a Broker peer overflows and the "disconnect" overflow
policy is in use, Zeek now only attempts to re-establish peerings when the
node observing the overflow originally established the peering. That is,
re-peering is now only attempted in consistency with the underlying Broker
peering topology. This avoids pointless connection attempts to ephemeral TCP
client-side ports, which clould clutter the Broker logs.
Removed Functionality
---------------------