Page 1 of 2
Nagios XI Execution Dependency via GUI
Posted: Mon Nov 10, 2014 1:09 pm
by JakeHatMacys
Hello, I'd like to set up an Execution dependency on a Service Monitor that depends on the host being in a good / green state before running. Not really seeing how to do this via the GUI in Nagios XI. Does anyone have a doc or can point in the direction on how to do this with XI? Or is this something that has to be configured in Core???
Re: Nagios XI Execution Dependency via GUI
Posted: Mon Nov 10, 2014 2:04 pm
by lmiltchev
You can add a service dependency by going to: CCM->Advanced->Service Dependencies->Add New
Note: For more info, select "execution_failure_criteria" from the "Help & Documentation" drop-down menu. You can also review the Nagios Core documentation on host and service dependencies here:
http://nagios.sourceforge.net/docs/nagi ... ncies.html
Hope this helps.
Re: Nagios XI Execution Dependency via GUI
Posted: Tue Nov 11, 2014 8:50 am
by JakeHatMacys
Thanks that did help, I still haven't quite got it to work yet though. Maybe I'm reading this wrong. But I want the URL Content check to not run once I take down the URL:
Re: Nagios XI Execution Dependency via GUI
Posted: Tue Nov 11, 2014 8:52 am
by JakeHatMacys
This is my current config. The URL Content is set under the "Manage Services" (I don't want it to run when dependency is crit) and the URL is set in the Manage Service Dependency tab. I take down the URL and the URL content still runs when the URL is in a critical state.
Any ideas? Am I interpreting this wrong?
Re: Nagios XI Execution Dependency via GUI
Posted: Tue Nov 11, 2014 10:59 am
by lmiltchev
Go to the CCM->Service Dependencies, click on the "View Text Config" next to "Service Dependency Test", copy/paste your config, so that we can take a look at it.
Re: Nagios XI Execution Dependency via GUI
Posted: Tue Nov 11, 2014 3:30 pm
by JakeHatMacys
define servicedependency {
dependent_host_name mt000xsksm105
dependent_service_description HTTP
host_name mt000xsksm105
service_description _SiteScope_Content URL Content
inherits_parent 1
execution_failure_criteria w,u,c,p,
notification_failure_criteria w,u,o,p,
dependency_period 24x7
}
Re: Nagios XI Execution Dependency via GUI
Posted: Tue Nov 11, 2014 4:49 pm
by lmiltchev
Aren't these reversed?
You have:
Code: Select all
dependent_service_description HTTP //This directive is used to identify the description of the dependent service.
service_description _SiteScope_Content URL Content // This directive is used to identify the description of the service that is being depended upon (also referred to as the master service)
I believe, you need to have:
Code: Select all
dependent_service_description _SiteScope_Content URL Content
service_description HTTP
Re: Nagios XI Execution Dependency via GUI
Posted: Wed Nov 12, 2014 10:37 am
by JakeHatMacys
lmiltchev wrote:Aren't these reversed?
You have:
Code: Select all
dependent_service_description HTTP //This directive is used to identify the description of the dependent service.
service_description _SiteScope_Content URL Content // This directive is used to identify the description of the service that is being depended upon (also referred to as the master service)
I believe, you need to have:
Code: Select all
dependent_service_description _SiteScope_Content URL Content
service_description HTTP
So you're saying:
define servicedependency {
dependent_host_name mt000xsksm105
dependent_service_description _SiteScope_Content URL Content
host_name mt000xsksm105
service_description HTTP
inherits_parent 1
execution_failure_criteria w,u,c,p,
notification_failure_criteria w,u,o,p,
dependency_period 24x7
}
Trying this now
Re: Nagios XI Execution Dependency via GUI
Posted: Wed Nov 12, 2014 1:47 pm
by lmiltchev
Sure. Let us know how it went.
Re: Nagios XI Execution Dependency via GUI
Posted: Wed Nov 12, 2014 3:09 pm
by JakeHatMacys
Worked well, for some reason my brain was processing things backwards.
So random question, is there an easy way to reset the attempts counter in Nagios??? I'm not seeing an obvious way to do it, I did realize the dependency didn't kick in until the dependent monitor hit a Hard state. That's why I thought it was working before when I had reversed them originally (which ended up being correct).