Re: [Zeek-Dev] Proposal: Improve Zeek's log-writing system with batch support and better status reporting

2020-07-15 Thread Bob Murphy
> On Jul 15, 2020, at 1:09 AM, Robin Sommer wrote: > > On Thu, Jul 09, 2020 at 18:19 -0700, Bob Murphy wrote: > >> Proposed Solution: Add a new optional API for writing a batch all at once, >> while >> still supporting older log writers that don't need to write batches. > > That sounds good

Re: [Zeek-Dev] Proposal: Make Zeek's debug logging thread-safe

2020-07-15 Thread Bob Murphy
> > On Jul 15, 2020, at 12:52 AM, Robin Sommer wrote: > Reading through this thread, I'm wondering if we should focus on > improving identification of log lines in terms of where they come from > and when they were generated, while keeping to go through the existing > mechanism of sending

Re: [Zeek-Dev] Proposal: Improve Zeek's log-writing system with batch support and better status reporting

2020-07-15 Thread Robin Sommer
On Thu, Jul 09, 2020 at 18:19 -0700, Bob Murphy wrote: > Proposed Solution: Add a new optional API for writing a batch all at once, > while > still supporting older log writers that don't need to write batches. That sounds good to me, a PR with the proposed API would be great. > a. For

Re: [Zeek-Dev] Proposal: Make Zeek's debug logging thread-safe

2020-07-15 Thread Robin Sommer
Reading through this thread, I'm wondering if we should focus on improving identification of log lines in terms of where they come from and when they were generated, while keeping to go through the existing mechanism of sending messages back to main process for output (so that we don't need the