2 commits

Author	SHA1	Message	Date
Arne Welzel	9a7678f15a	cluster/Backend: Fallback to current network time when current event has not timestamp ... When a WebSocket client sends an event to Zeek without explicit network timestamp metadata, Zeek would use -1.0 as a timestamp for any events published while handling this event. Instead, it seems far more sensible to use the current network time in that scenario.	2025-08-20 19:56:50 +02:00
Arne Welzel	01fe022e07	cluster/serializer/broker: Do not send empty metadata vectors around ... Event when there's no metadata attached to an event, we'd still use the constructor passing an empty metadata vector, resulting in an on-the-wire representation with an empty trailing vector. Particularly visible when just snooping events via websocat. There also seems to be some bug with the timestamp -1 handling.	2025-08-20 19:55:38 +02:00