ok let me try to explain this some more…
There are 3 host states UP/DOWN/UNREACHABLE
We use ping to determin our host status and get notified if the host goes DOWN. We dont notify if the host becomes UNREACHABLE because we know whats blocking access to that host is another host which will show DOWN and we are notified by that host instead. We are not interested in UNREACHABLE hosts because the host that is DOWN is what needs dealing with first.
Basically we want to do the same with services on a host when that host goes DOWN. We do not want to be notified about a service being DOWN because check_nt cannot reach the service because the host is DOWN.
Now you can set up host dependancies and hosts become UNREACHABLE when the dependant host goes DOWN.
Now you can set up service dependancies and services become UNKNOWN when the dependant service goes DOWN
But there are no config options to set a service dependant on a host?..
Am I correct in this thinking?
What I’m looking at doing is when a host goes down the services on that host become UNKNOWN rather than DOWN so that I can filter out UNKNOWN notifications for services.
So I would guess, because there is no config way of doing what I’m after I would have to set up some sort of command/macro so that when a host goes down it disables all service checks on that host and sets all service status to UNKNOWN. Then when the host comes UP then the service checks are re-enabled and services are forced to do a check.
Thank you for your input kosarajudeepak and I know what you are saying and yes I can stop email notifications going out based on host status but we use various tools that read nagios and these tools show a lot of RED when a host goes down because services are also DOWN on that host.
If I’m wrong then please correct me if I’m has anyone got any help on how I would setup this commands and macros to do what I am after?