Thanks for the response Martin! In reading the documentation you discuss limitations presented by using the crontab-style format for listing these windows by saying "We will address this limitation in a future release and convert the test scheduler from serial polling into a parallel non-blocking scheduler where checks are guaranteed to run on time and with seconds resolution."
Is this change going to include changing the format to something that could possibly allow the use of any poll window or even multiple poll windows? We will use cron as you suggest, but it would be pretty nice if we could do this within monit. Thanks Bill On Thu, Mar 14, 2013 at 2:19 PM, Martin Pala <[email protected]> wrote: > Hello, > > multiple "every" statements per service are not supported currently, as a > workaround you can enable/disable the service monitoring externally via > monit CLI, for example add the following to cron: > > 0 0 * * * /usr/bin/monit unmonitor myservice > 30 1 * * * /usr/bin/monit monitor myservice > > You can also (un)monitor all services: > > monit unmonitor all > > or specific service group (using -g option): > > monit -g myservicegroup unmonitor > > > Regards, > Martin > > > On Mar 13, 2013, at 5:40 PM, Bill Sirinek <[email protected]> wrote: > > > Is it possible to set service poll times to be something more complex > than can be specified in one "EVERY" or "NOT EVERY" statement? > > > > For example, I have something I'd like to not alert on from 00:00 - > 01:30 each night. > > > > Since monit does not know about seconds, my intent here was to tell > monit not check the service if the current time is 00:00-01:29. > > > > Doing the following does not work: > > > > not every "* 0 * * *" > > not every "0-29 1 * * *" > > > > When listing multiple every/not every statements, only the last listed > poll time exclusion is acted on, so in this case it is 01:00-01:29. > > > > Is there a way to make this work? The best I could find in the email > archive was someone showing how to specify a complex time range with a > slash. While that might be valid syntax in Linux's cron daemon, it is not > within monit. > > > > Thanks > > > > Bill > > > > > > > > -- > > To unsubscribe: > > https://lists.nongnu.org/mailman/listinfo/monit-general > > > -- > To unsubscribe: > https://lists.nongnu.org/mailman/listinfo/monit-general >
-- To unsubscribe: https://lists.nongnu.org/mailman/listinfo/monit-general
