Ack/Downtime on multiple hosts/services

[Jason Frisvold]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Lee Azzarello wrote:
> I would think of this as more of a policy question than a technical
> one. If a large number of hosts and services are going down often
> enough for you to need a batch processing script to trigger nagios to
> recognize down time, perhaps your monitoring plan could be altered?
> You can define a check time period that only watches for critical
> states when the hosts are expected to be online. You can also change
> which services are checked for the group of hosts that have a high
> amount of maintenance periods.

It's not a common occurrence by any means, but it does happen.  For
instance, we have a scheduled downtime each year when the power system
is worked on, parts replaced, etc.  During that downtime, a large number
of devices will be down, and it would be nice to be able to schedule
them all down in one fell swoop.

> -lee

- --
- ---------------------------
Jason Frisvold
Network Engineer
frisvolj at lafayette.edu
- ---------------------------
"What I cannot create, I do not understand"
   - Richard Feynman
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with CentOS - http://enigmail.mozdev.org

iD8DBQFJlZbhO80o6DJ8UvkRAmDsAJ9WuaAQ8UxE5DTiv/0yXpTjSzHypgCffV4t
0GbNrOBL8W6w9G08F/azpHE=
=UrqG
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
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