mirror of
https://github.com/zeek/zeek.git
synced 2025-10-02 06:38:20 +00:00
742f7fe340
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. |
||
|---|---|---|
| .. | ||
| agent | ||
| controller | ||
| node | ||
| supervisor | ||
| __load__.zeek | ||
| config.zeek | ||
| log.zeek | ||
| persistence.zeek | ||
| request.zeek | ||
| types.zeek | ||
| util.zeek | ||