Hi,
Marc Powell a écrit:
Our ideas of accuracy would seem to differ ;)
Sometimes, in life, it's necessary to be able to say : I don't know.
When a host is simply powered off, or unreachable due to network/wan
failure, Nagios actually displays all the service checks with the
results
Hi Mark, thank you for your answer,
Marc Powell a écrit:
Nagios is first and foremost a service monitor, not a host monitor.
Host monitoring is only necessary, as far as nagios is concerned, for
two reasons --
- notification supression. If the host is down, don't notify about
the
Toussaint OTTAVI a écrit:
Following this idea, I will investigate the following :
- Hosts associated themselves with parent/child relationship according
to WAN topology (already working)
- For each host, I will create a parent service with only a
check_alive command
- Every other service
On Dec 9, 2008, at 5:35 AM, Toussaint OTTAVI wrote:
I agree with you. Parenting / unreachable logic is a very good
thing. But I think it should allow to declare a service as a child
of its host. This parent/child logic can suppress 'notifications'. I
think it could also suppress the
Hi list,
I've been investigating this problem for a while, but I couldn't find a
good solution.
* Example situation :
Assume I have one host with 20 service checks.
* Problem :
If the host becomes DOWN, Nagios still continues to do service checks on
this host. So, after a while, all the
On Dec 8, 2008, at 11:38 AM, Toussaint OTTAVI wrote:
Hi list,
I've been investigating this problem for a while, but I couldn't
find a good solution.
* Example situation :
Assume I have one host with 20 service checks.
* Problem :
If the host becomes DOWN, Nagios still continues to do
