schedule downtime for host AND it's services

[Richard Luys]

On Tue, 31 Aug 2004 12:35:05 +0200, Sand Philipp <Philipp.Sand at sycor.de> 
wrote:
Hello Phillip,

> Hi,
>
> is it possible to trigger a downtime for all services of a host when you 
> schedule the downtime for the host. I got some Servers with about 15 
> Service checks, and it's a pretty dumb work when you have to schedule a 
> downtime for each service each time you have to reboot the server...
>
> I'm currently using Nagios 2.0a1, I've ssen the feature to trigger a 
> downtime for all children of a host, but not for all services of a host 
> :-/
> Am I blind or isn't it possible to trigger the downtime for the services?
>
I am not using 2.0a1 yet, but I think it works the same as in 1.2

When you schedule downtime for a host, the services are also supposed to 
be down, there is no need to schedule them separately (makes sense, 
doesn't it? When a host is down, you don't expect the services to still be 
up...)

Downtime scheduling works even in parent-child relationship. When a router 
goes down, which is parent for a lot of servers with a lot of services, 
and you need to take the router down for maintenance, just schedule 
downtime for the router. During the downtime period of the router, all 
notifications for this router, it's services AND for all hosts depending 
on this router (ie hosts that are 'children' of this router from Nagios' 
perspective) are supressed.

We've tested this last week, and it works great!

Hope this helps,
Richard

> Help would be appreciated!
See above ;-)


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at 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