Page 2 of 2
Re: Service checks when host is down
Posted: Tue Mar 19, 2013 11:03 am
That looks reasonable ... I will try this out.
One thing remaining, the dummy-checker itself will create additional 'critical' events in nagios.
Is there anything we can do with this (ie to stop reporting to nagios and hence cluttering up the display) ie is it possible to hide this from view and from the stats (ie count of critical services will not change if dummy-servic e is critical).
I know this is probably stretching it a bit.
Regards
Liam
Re: Service checks when host is down
Posted: Tue Mar 19, 2013 12:21 pm
by abrist
Not really, as you need the check's state to change for the dependency purposes. At least you would only get 1 host and 1 service fail per failed host instead of an additional chunk of failed services.
Re: Service checks when host is down
Posted: Tue Mar 19, 2013 3:43 pm
thanks you all for your input. I will setup the devices as indicated.
Thanks
Liam
Re: Service checks when host is down
Posted: Tue Mar 19, 2013 3:48 pm
by slansing
Great, let us know if we can be of further help.
Re: Service checks when host is down
Posted: Tue Mar 26, 2013 8:57 am
by vgavara
[email protected] wrote:As suggested I raised an enhancement request...
[*]One service cannot be dependent on one host, just on one (or more) service(s) and what we're talking about is making one or more services dependent on their host.
All the services I test with a given host are very specific to that host (ie most are wmi checks using check_wsc as the engine), memory utilisation, processor utilisation, service running, processes running, etc. It makes sence for us to consider services dependant on their host. In fact the vast majority of all the tests we have configured are of this type. The only tests outside of this are a small number of tests on a Microsoft Cluster, DHCP,DNS and AD Domain servers, which I agree would fall under this model.
Does this mean that a different service model or a modification of the current service model is required to satisfy these needs?
Maybe I didn't expose it quite correctly. What I meant when said "One service cannot be dependent on one host" is that, based on the Nagios documentation covering services dependencies, you cannot configure a service being dependent on one host, ie, you cannot create a dependency rule saying "service A1 depends on host A".
I think that the real solution might be that future versions of the core would allow just that: Allowing that a service status was dependent on a host status. Tweaking tge first example in
http://nagios.sourceforge.net/docs/3_0/ ... ncies.html, I mean something like:
Code: Select all
define servicedependency{
host_name Host B
service_description Service D
dependent_host_name Host B
execution_failure_criteria d,u
notification_failure_criteria d,u
}
Re: Service checks when host is down
Posted: Tue Mar 26, 2013 9:01 am
by scottwilkerson
You can feel free to add this as a feature request on the Core tracker if you like
http://tracker.nagios.org/
If there is enough traction it may get added.