zeek/scripts/base/frameworks/cluster
Christian Kreibich 1bd658da8f Support for log filter policy hooks
This adds a "policy" hook into the logging framework's streams and
filters to replace the existing log filter predicates. The hook
signature is as follows:

    hook(rec: any, id: Log::ID, filter: Log::Filter);

The logging manager invokes hooks on each log record. Hooks can veto
log records via a break, and modify them if necessary. Log filters
inherit the stream-level hook, but can override or remove the hook as
needed.

The distribution's existing log streams now come with pre-defined
hooks that users can add handlers to. Their name is standardized as
"log_policy" by convention, with additional suffixes when a module
provides multiple streams. The following adds a handler to the Conn
module's default log policy hook:

    hook Conn::log_policy(rec: Conn::Info, id: Log::ID, filter: Log::Filter)
            {
            if ( some_veto_reason(rec) )
                break;
            }

By default, this handler will get invoked for any log filter
associated with the Conn::LOG stream.

The existing predicates are deprecated for removal in 4.1 but continue
to work.
2020-09-30 12:32:45 -07:00
..
nodes Fix closing timestamp of rotated log files in supervised-cluster mode 2020-08-25 17:06:10 -07:00
__load__.zeek BrokerStore<->Zeek tables: &backend works for in-memory stores. 2020-07-01 16:38:10 -07:00
broker-stores.zeek Merge remote-tracking branch 'origin/topic/johanna/table-changes' 2020-07-21 15:39:39 +00:00
main.zeek Support for log filter policy hooks 2020-09-30 12:32:45 -07:00
pools.zeek Fix Broker topics used to uniquely identify cluster nodes 2020-04-10 14:36:00 -07:00
README More bro-to-zeek renaming in scripts and other files 2019-05-16 02:36:41 -05:00
setup-connections.zeek unused variables found via use-def analysis (plus an indentation micro-nit) 2020-04-25 18:06:47 -07:00

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