In short, if a host is set with notification from 8am-5pm, and a service that 
checks that host is set to 24hrs, will a failed service check notify anyone 
outside of 8am-5pm?

In a bit more detail, looking at 
http://nagios.sourceforge.net/docs/3_0/notifications.html and the paragraph 
about "The fourth host or service filter...." does the notification only go out 
on the "intersection" of the two schedules?  Or does the service notification 
schedule apply for service check and the host notification schedule apply for 
host check, and the two have nothing to do with each other otherwise?

As a concrete example, I want to do a simple check_load on two hosts, one 
development server and one production server.  The dev server, I only want to 
get paged on check_load between 8a-5p, whereas the production server I want to 
be paged 24x7.  I create two hosts, devserver and prodserver, w/a notification 
schedule of 8a-5p, and 24x7, respectively for host check.   Right now, I also 
have two separate service checks: check_load_dev and check_load_prod, the first 
w/a notification schedule of 8a-5p and the other 24x7.

I'm basically shooting to only have one check_load service check, it'll clean 
up my nagios services listing alot, not to have one -dev and one -prod check 
for the same thing, w/the only difference being the service check's 
notification time.

Thank you,
PH

==
Paul Hirose
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null

Reply via email to