I'm trying to figure out the best way to do this, yet keep things as
simple as possible.
Say I have a server called Saturn running VMWare. I'm monitoring this
server with Nagios.
I also have three VM's on Saturn: Jupiter, Mars, and Pluto
I want to suppress all host and service alerts on Jupiter, Mars, & Pluto
if the host Saturn is down (unreachable). I do NOT want to suppress host
or service alerts from Jupiter, Mars, and Pluto if the VMWare processes
(services) are down on Saturn. Basically, if my VM server is completely
unreachable, don't bother me about its client VM's.
Am I better off doing this with a host dependency? Something like:
*define hostdependency {
host_name Host B
dependent_host_name Host C
notification_failure_criteria d,u
}
*
Or am I better off defining Saturn as the parent of the VM's in the host
config? Something like:
*define host {
host_name jupiter
use VMs
alias jupiter
address 172.26.251.60
parents saturn, tpdmzsw1
}*
I've successfully used the "parents" directive to define network
topology, so I would think this would work. What might be the risks of
defining both?
--
A. Davis
Email: ncc...@gmail.com
"There is no limit to what a man can accomplish
if he doesn't care who gets the credit." - Ronald Reagan
------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
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
