zeek/scripts/base/frameworks/broker
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
..
__load__.zeek Rename all scripts to have ".zeek" file extension 2019-04-11 21:12:40 -05:00
log.zeek Support for log filter policy hooks 2020-09-30 12:32:45 -07:00
main.zeek GH-780: Prevent log batches from indefinite buffering 2020-02-05 13:06:52 -08:00
README More bro-to-zeek renaming in scripts and other files 2019-05-16 02:36:41 -05:00
store.zeek Merge remote-tracking branch 'origin/topic/johanna/table-changes' 2020-07-21 15:39:39 +00:00

The Broker communication framework facilitates connecting to remote Zeek
instances to share state and transfer events.