Roberto Nunnari wrote:
Hi Gerald.
Ortner, Gerald wrote:
What host/service check interval/max check attempts do you use?
Maybe the host check interval is much longer than the service check interval.
If the services become hard state critical before the host check does, the
service
Hi Gerald.
Ortner, Gerald wrote:
What host/service check interval/max check attempts do you use?
Maybe the host check interval is much longer than the service check interval.
If the services become hard state critical before the host check does, the
service notifications will be sent, as
Hi Benny.
C. Bensend wrote:
Yesterday for instance, a host went down because of a hd controller
failure, and I received 22 sms..
I apologize if this has already been stated, I haven't been following
this thread too closely.
When this happened, was the host down *in a network sense*, or
Hi Mark.
Frost, Mark {PBC} wrote:
Maybe I'm missing something but I thought that suppressing notifications for
services on the same host when the host goes down is the default behavior.
It's only when you have to suppress notifications from different hosts that
you need host/service
Terry Carmen wrote:
Quoting Assaf Flatto nag...@flatto.net:
Any hint/advice/guidance is very welcome.
Thank you and best regards.
Robi
check out service dependencies
http://nagios.sourceforge.net/docs/3_0/dependencies.html
I'm in the same boat.
This should be very simple, but
Assaf Flatto wrote:
Martin Hugo wrote:
Hi Robi,
I have never done it but I know you can make hosts/services children that
will not report if the parent is down.
Hope this puts you on the right track.
Marty
-Original Message-
From: Roberto Nunnari
Hi,
I found a solution by adding a service dependency on the nrpe daemon.
This works well with a single dependency definition for standard checks I like
to have on all server but you need to define additional service dependencie for
every service.
When you work with hostgroups you can use
What host/service check interval/max check attempts do you use?
Maybe the host check interval is much longer than the service check interval.
If the services become hard state critical before the host check does, the
service notifications will be sent, as Nagios isn't aware of the host problem.
I
Hi all.
Some time ago, I've installed and configured nagios to monitor our IT
infrastructure.
It works very well and we're happy with it.
There's still one problem though:
When a host goes down, nagios sends notifications not only for host
down, but also for all services running on that host.
Hi Robi,
I have never done it but I know you can make hosts/services children that will
not report if the parent is down.
Hope this puts you on the right track.
Marty
-Original Message-
From: Roberto Nunnari [mailto:roberto.nunn...@supsi.ch]
Sent: Thursday, May 26, 2011 12:47 PM
To:
Martin Hugo wrote:
Hi Robi,
I have never done it but I know you can make hosts/services children that
will not report if the parent is down.
Hope this puts you on the right track.
Marty
-Original Message-
From: Roberto Nunnari [mailto:roberto.nunn...@supsi.ch]
Sent: Thursday,
Quoting Assaf Flatto nag...@flatto.net:
Any hint/advice/guidance is very welcome.
Thank you and best regards.
Robi
check out service dependencies
http://nagios.sourceforge.net/docs/3_0/dependencies.html
I'm in the same boat.
This should be very simple, but I'm probably just missing
Maybe I'm missing something but I thought that suppressing notifications for
services on the same host when the host goes down is the default behavior.
It's only when you have to suppress notifications from different hosts that you
need host/service dependencies.
Mark
-Original
13 matches
Mail list logo
