Hey Lennart, Two example scenarios:
1) I'm monitoring a job that runs at 8AM. It finishes anywhere between 8:10-8:15AM. I'm using nxlog (parsing a custom log file) and sending to graylog to verify/alert if the job has failed. It's inefficient to have that stream active for the entire day (wasting CPU resources) when it's only required during an estimated window of time. 2) I monitor database backups with graylog (success messages). A script queries elasticsearch every 10 minutes to see if the backup completed successfully. Once it has been confirmed that the backup completed, immediately start compressing the backup for off-site storage (this eliminates needing to schedule compression jobs). The backup completion window is a ~two hour range at most. I realize there are better solutions for each of these scenarios, but centrally managing all alerts is a wonderful thing. Having a schedule for specific streams could be useful in many different scenarios. Thanks! Zi On Friday, November 14, 2014 12:01:17 PM UTC-5, lennart wrote: > > Hey Zi, > > thanks for the suggestion! Can you elaborate your use case for this? > > Thanks, > Lennart > > On Fri, Nov 14, 2014 at 4:01 PM, Zi Dvbelju <[email protected] > <javascript:>> wrote: > > I have a quick suggestion for streams - implement optional schedules > during > > which a stream can be active/paused. Would be an incredibly nice > feature! > > > > Keep up the good work, absolutely loving Graylog2. > > > > -- > > You received this message because you are subscribed to the Google > Groups > > "graylog2" group. > > To unsubscribe from this group and stop receiving emails from it, send > an > > email to [email protected] <javascript:>. > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "graylog2" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
