But that means I need a different notification period for each of my services
that have downtime. I know that might seem like an unnecessary requirement,
but if I have to set up a notification timeperiod for each of these, it means
that I could either: a) have a lot of time periods, or b) lose the tie between
the service and timeperiod.
What I would prefer is to have only a few timeperiods that I assign everything
to, and have "exceptions" to the rule.
Does that make sense? It may be a low requirement RFE, but it would be great
to have that.
--
-bk
Quoting Russell Scibetti :
> The way Nagios handles this is through the notification_timeperiod
> setting of a service/host. You can create a timeperiod with that
> section of time missing, for example:
>
> define timeperiod{
> name thurday_dt_timperiod
> monday 00:00-24:00
>
> .
> thursday 00:00-17:00, 19:00-24:00
> ...
> }
>
> So for every day except thursday, you set to 00:00-24:00, and for
> thursday you leave out the 2 hours you know if will be down. Use the
> name of this timeperiod definition for your notification_timeperiod setting.
>
> Russell Scibetti
>
> Brandon Knitter wrote:
>
> >I read up on dowtime via:
> http://nagios.sourceforge.net/docs/1_0/downtime.html
> >
> >What I found missed was repeated downtime. For instance, if I know that
> every
> >Thursday between 5pm and 7pm that a service will be offline, I really don't
>
> >want to alert on it, but I do want to monitor it (good for looking at trends
>
> >like the length of the downtime in each period).
> >
> >Did I miss something, or is this feature lacking?
> >
>
> --
> Russell Scibetti
> Quadrix Solutions, Inc.
> http://www.quadrix.com
> (732) 235-2335, ext. 7038
>
>
>
>
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]