mirror of
https://github.com/zeek/zeek.git
synced 2025-10-02 06:38:20 +00:00
Merge remote-tracking branch 'origin/topic/awelzel/4177-4178-custom-event-metadata-part-2'
* origin/topic/awelzel/4177-4178-custom-event-metadata-part-2: Event: Bail on add_missing_remote_network_timestamp without add_network_timestamp btest/plugin: Test custom metadata publish NEWS: Add note about generic event metadata cluster: Remove deprecated Event constructor cluster: Remove some explicit timestamp handling broker/Manager: Fetch and forward all metadata from events Event/init-bare: Add add_missing_remote_network_timestamp logic cluster/Backend/DoProcessEvent: Use generic metadata, not just timestamps cluster/Event: Support moving args and metadata from event cluster/serializer/broker: Support generic metadata cluster/Event: Generic metadata support Event: Use -1.0 for undefined/unset timestamps cluster: Use shorter obj_desc versions Desc: Add obj_desc() / obj_desc_short() overloads for IntrusivePtr
This commit is contained in:
commit
0a34b39e7a
28 changed files with 682 additions and 99 deletions
|
@ -601,6 +601,16 @@ export {
|
|||
## might be a value before the network_time() when the event
|
||||
## was actually dispatched.
|
||||
const add_network_timestamp: bool = F &redef;
|
||||
|
||||
## By default, remote events without network timestamp metadata
|
||||
## will yield a negative zeek:see:`current_event_time` during
|
||||
## processing. To have the receiving Zeek node set the event's
|
||||
## network timestamp metadata with its current local network time,
|
||||
## set this option to true.
|
||||
##
|
||||
## This setting is only in effect if :zeek:see:`EventMetadata::add_network_timestamp`
|
||||
## is also set to true.
|
||||
const add_missing_remote_network_timestamp: bool = F &redef;
|
||||
}
|
||||
|
||||
module FTP;
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue