zeek/testing/btest/Baseline/coverage.init-default/missing_loads
Christian Kreibich ead6134501 Add backpressure disconnect notification to cluster.log and via telemetry
This adds a Broker-specific script to the cluster framework, loaded only when
Zeek is running in cluster mode. It adds logging in cluster.log as well as
telemetry via a metrics counter for Broker-observed backpressure disconnects.

The new zeek_broker_backpressure_disconnects counter, labeled by the neighboring
peer that the reporting node has determined to be unresponsive, counts the
number of unpeerings for this reason.

Here the node "worker" has observed node "proxy" falling behind once:

# HELP zeek_broker_backpressure_disconnects_total Number of Broker peering drops due to a neighbor falling too far behind in message I/O
# TYPE zeek_broker_backpressure_disconnects_total counter
zeek_broker_backpressure_disconnects_total{endpoint="worker",peer="proxy"} 1

Includes small btest baseline update to reflect @load of a new script.
2024-12-06 15:18:05 -08:00

15 lines
654 B
Text

### BTest baseline data generated by btest-diff. Do not edit. Use "btest -U/-u" to update. Requires BTest >= 0.63.
-./frameworks/cluster/broker-backpressure.zeek
-./frameworks/cluster/broker-stores.zeek
-./frameworks/cluster/nodes/logger.zeek
-./frameworks/cluster/nodes/manager.zeek
-./frameworks/cluster/nodes/proxy.zeek
-./frameworks/cluster/nodes/worker.zeek
-./frameworks/cluster/setup-connections.zeek
-./frameworks/cluster/supervisor.zeek
-./frameworks/intel/cluster.zeek
-./frameworks/netcontrol/cluster.zeek
-./frameworks/openflow/cluster.zeek
-./frameworks/packet-filter/cluster.zeek
-./frameworks/sumstats/cluster.zeek
-./init-supervisor.zeek