mirror of
https://github.com/zeek/zeek.git
synced 2025-10-02 06:38:20 +00:00
b96a4276eb
The role isn't just about logging, it can also act as a general indicator to key in on in role-specific code elsewhere, such as @if.
27 lines
1.1 KiB
Text
27 lines
1.1 KiB
Text
##! Management framework configuration settings common to agent and controller.
|
|
##! This does not include config settings that exist in both agent and
|
|
##! controller but that they set differently, since setting defaults here would
|
|
##! be awkward or pointless (since both node types would overwrite them
|
|
##! anyway). For role-specific settings, see management/controller/config.zeek
|
|
##! and management/agent/config.zeek.
|
|
|
|
@load ./types
|
|
|
|
module Management;
|
|
|
|
export {
|
|
## The role of this process in cluster management. Use this to
|
|
## differentiate code based on the type of node in which it ends up
|
|
## running.
|
|
const role = Management::NONE &redef;
|
|
|
|
## The fallback listen address if more specific adddresses, such as
|
|
## the controller's :zeek:see:`Management::Controller::listen_address`
|
|
## remains empty. Unless redefined, this uses Broker's own default
|
|
## listen address.
|
|
const default_address = Broker::default_listen_address &redef;
|
|
|
|
## The retry interval for Broker connnects. Defaults to a more
|
|
## aggressive value compared to Broker's 30s.
|
|
const connect_retry = 1sec &redef;
|
|
}
|