Re: [Zeek-Dev] Log archival (Re: Zeek Supervisor: designing client and log archival) behavior

2020-07-01 Thread Jon Siwek
On Wed, Jul 1, 2020 at 1:59 AM Robin Sommer wrote: > > > Log::default_rotation_dir > > Seems we should then set this to "." by default, and have the cluster > framework override it. Yes, exactly. > Once moved, I suppose we would continue to optionally run a > post-processor, right? For a

Re: [Zeek-Dev] Zeek Supervisor Command-Line Client

2020-07-01 Thread Robin Sommer
On Tue, Jun 30, 2020 at 14:29 -0700, Jon Siwek wrote: > Maybe the important observation is that the logic can be performed > anywhere that has access to the Zeek-Supervisor process. Agree. > So where we put the logic at this point may not be important. If we > can find a single-best-place for

[Zeek-Dev] Supervisor client (Re: Zeek Super-isor: designing client and log archival behavior)

2020-07-01 Thread Robin Sommer
> * https://github.com/zeek/zeek/wiki/Zeek-Supervisor-Client Some thoughts on the commands: > $ zeekc status [all | ] > Do we need to include any other metrics in the returned status? That information is mostly static, would be nice to get some dynamic information in there as well, like

[Zeek-Dev] Log archival (Re: Zeek Supervisor: designing client and log archival) behavior

2020-07-01 Thread Robin Sommer
On Tue, Jun 30, 2020 at 01:39 -0700, Jon Siwek wrote: > * https://github.com/zeek/zeek/wiki/Zeek-Supervisor-Log-Handling This overall sounds good to me. Some notes & questions: > Log Rotation > To help bridge/replace Step (4) and (5), suggest adding a new option: >