mirror of
https://github.com/zeek/zeek.git
synced 2025-10-03 07:08:19 +00:00
b80298a9ad
Instead of assuming the logger node always has the name "logger", now broctl will set a boolean which the cluster framework scripts can use to determine if there is a logger node or not. Also removed one line from the manager node script, because it has to do with logging, which the logger.bro script handles.
26 lines
999 B
Text
26 lines
999 B
Text
##! This is the core Bro script to support the notion of a cluster manager.
|
|
##!
|
|
##! The manager is passive (the workers connect to us), and once connected
|
|
##! the manager registers for the events on the workers that are needed
|
|
##! to get the desired data from the workers. This script will be
|
|
##! automatically loaded if necessary based on the type of node being started.
|
|
|
|
##! This is where the cluster manager sets it's specific settings for other
|
|
##! frameworks and in the core.
|
|
|
|
@prefixes += cluster-manager
|
|
|
|
## Don't do any local logging since the logger handles writing logs.
|
|
redef Log::enable_local_logging = F;
|
|
|
|
## Turn on remote logging since the logger handles writing logs.
|
|
redef Log::enable_remote_logging = T;
|
|
|
|
## Log rotation interval.
|
|
redef Log::default_rotation_interval = 24 hrs;
|
|
|
|
## Use the cluster's delete-log script.
|
|
redef Log::default_rotation_postprocessor_cmd = "delete-log";
|
|
|
|
## We're processing essentially *only* remote events.
|
|
redef max_remote_events_processed = 10000;
|