On 9 Jul 2020, at 16:57, Bob Murphy wrote:
> Right now, if you try to use Zeek's debug logging facilities in
> DebugLogger.h concurrently from multiple threads, the contents of
> debug.log can get mixed up and look like like "word salad".
Is there a reason why you didn’t just use the Debug
Summary
This proposal is aimed at solving two intertwined problems in Zeek's log-
writing system:
Problem: Batch writing code duplication
- Some log writers need to send multiple log records at a time in "batches".
These include writers that send data to elasticsearch, splunk hec, kinesis,
Right now, if you try to use Zeek's debug logging facilities in DebugLogger.h
concurrently from multiple threads, the contents of debug.log can get mixed up
and look like like "word salad".
I've been working on log writers for Zeek. Those operate in different threads,
and using Zeek's current
Hello everyone,
If you followed last year’s Zeek Week, you might be aware that we have
been working on a new way to more easily distribute Zeek Table content
in a cluster setup. We now have a working prototype - and I would be
happy for feedback if someone wants to start playing with it.
We
