zeek/scripts/policy
Christian Kreibich 742f7fe340 Management framework: add auto-enumeration of metrics ports
This is quite redundant with the enumeration for Broker ports,
unfortunately. But the logic is subtly different: all nodes obtain a telemetry
port, while not all nodes require a Broker port, for example, and in the metrics
port assignment we also cross-check selected Broker ports. I found more unified
code actually harder to read in the end.

The logic for the two sets remains the same: from a start point, ports get
enumerated sequentially that aren't otherwise taken. These ports are assumed
available; there's nothing that checks their availability -- for now.

The default start port is 9000. I considered 9090, to align with the Prometheus
default, but counting upward from there is likely to hit trouble with the Broker
default ports (9999/9997), used by the Supervisor. Counting downward is a bit
unnatural, and shifting the Broker default ports brings subtle ordering issues.

This also changes the node ordering logic slightly since it seems more intuitive
to keep sequential ports on a given instance, instead of striping across them.
2024-07-08 23:05:24 -07:00
..
files/x509 Remove unified2 file analyzer 2022-08-19 14:05:00 +02:00
frameworks Management framework: add auto-enumeration of metrics ports 2024-07-08 23:05:24 -07:00
integration/collective-intel Remove barnyard2 integration scripts 2022-08-19 14:04:27 +02:00
misc Rework everything to access the prometheus-cpp objects more directly 2024-05-31 13:30:31 -07:00
protocols Merge branch 'topic/johanna/fix-logging-of-ssl-log-ext-in-some-cases' 2024-01-16 13:10:35 +00:00
tuning Move the options from policy/tuning/defaults to actual Zeek defaults, deprecate that package 2024-05-06 11:13:04 -07:00