zeek/scripts/base/frameworks/cluster
Arne Welzel 1d931b5a2f cluster/WebSocket: Include X-Application-Name in cluster.log
A bit ad-hoc formatting for the log, but that's mostly because cluster.log
only has message field and I don't think having a dedicated application_name
column is worth it. That could also be added by custom scripts if it's really
wanted for a given deployment.
2025-06-30 17:55:24 +02:00
..
nodes all: Fix typos identified by typos pre-commit hook 2023-06-13 17:57:32 +02:00
__load__.zeek cluster: Introduce telemetry component 2025-06-25 16:59:49 +02:00
broker-backpressure.zeek Add backpressure disconnect notification to cluster.log and via telemetry 2024-12-06 15:18:05 -08:00
broker-stores.zeek Revert "Merge remote-tracking branch 'origin/topic/vern/at-if-analyze'" 2023-05-31 09:20:33 +02:00
broker-telemetry.zeek Bugfix: accurately track Broker buffer overflows w/ multiple peerings 2025-05-07 17:27:38 -07:00
main.zeek cluster/WebSocket: Include X-Application-Name in cluster.log 2025-06-30 17:55:24 +02:00
pools.zeek Pre-compute the node topics for all pool entries. 2024-12-11 15:57:01 -05:00
README More bro-to-zeek renaming in scripts and other files 2019-05-16 02:36:41 -05:00
setup-connections.zeek cluster: Be noisy when attempting to connect to an unknown node 2024-12-12 13:01:04 +01:00
supervisor.zeek Remove deprecated Cluster::Node::interface field 2024-08-07 11:58:22 -07:00
telemetry.zeek cluster/telemetry: Move topic_normalization redef to zeromq 2025-06-26 15:22:11 +02:00

The cluster framework provides for establishing and controlling a cluster
of Zeek instances.