I've read over the Host and Service dependencies doc from Nagios Core, but I'm still a little fuzzy on things. This is what I'm trying to setup in the XI interface. I have 2 hosts:
CustomerABC - Internet Connection
Customer ABC - Some Device (passive checks)
I want to make it so that 'Customer ABC - Some Device' does not send alerts if 'Customer ABC - Internet Connection' is down.
I'm curious to see 1) How do actually set this up properly in XI gui, and 2) What the email alert actually looks like, if it mentions the dependencies in the email alert, etc.
Fingers cross for some simple guidance on this one. I couldn't find any XI docs on this, but perhaps I'm not looking hard enough?
Host Dependency question
Re: Host Dependency question
In the Host Management Window / Common Settings tab for the host named '...Some Device' click on the 'Manage Parents' button and add '...Internet Connection' -- this will ensure that Nagios will not send notifications about "...Some Device' if the parent device is down.
By default the message itself does not contain info about child-host devices but I believe it is possible to configure this to suit your needs.
However, be mindful of the distinction between parent/child relationships and dependencies, from the Nagios perspective.The OP from this thread provides a good example of such:
https://support.nagios.com/forum/viewto ... 74&p=37047
By default the message itself does not contain info about child-host devices but I believe it is possible to configure this to suit your needs.
However, be mindful of the distinction between parent/child relationships and dependencies, from the Nagios perspective.The OP from this thread provides a good example of such:
https://support.nagios.com/forum/viewto ... 74&p=37047
Be sure to check out the Knowledgebase for helpful articles and solutions!
Re: Host Dependency question
Here's a sample config:
In the CCM, this would look like this:
You can always select an option from the "Help & Documentation" menu for more information.
Code: Select all
define hostdependency {
# config_name test
dependent_host_name Customer ABC - Some Device
host_name CustomerABC - Internet Connection
inherits_parent 1
execution_failure_criteria d,
notification_failure_criteria d,
dependency_period 24x7
}You can always select an option from the "Help & Documentation" menu for more information.
Hostdependency - host name
This directive is used to identify the short name(s) of the host(s) that is being depended upon (also referred to as the master host). Multiple hosts should be separated by commas.
Parameter name: host_name
Required: yes (no, if a hostgroup is defined)
If both hosts are down, you will be notified only about "CustomerABC - Internet Connection" host but not about "Customer ABC - Some Device" as it is dependent on it. If you want to be notified about the "Customer ABC - Some Device" host, you could select "Notification failure criteria" = "n".Hostdependency - dependent host name
This directive is used to identify the short name(s) of the dependent host(s). Multiple hosts should be separated by commas
Parameter name: dependent_host_name
Required: yes (no, if a dependent hostgroup is defined)
Let us know if you have any more questions.Hostdependency - notification failure criteria
This directive is used to define the criteria that determine when notifications for the dependent host should not be sent out. If the master host is in one of the failure states we specify, notifications for the dependent host will not be sent to contacts. Valid options are a combination of one or more of the following:
o = fail on an UP state,
d = fail on a DOWN state,
u = fail on an UNREACHABLE state, and
p = fail on a pending state (e.g. the host has not yet been checked).
If you specify n (none) as an option, the notification dependency will never fail and notifications for the dependent host will always be sent out.
Example: If you specify d in this field, the notifications for the dependent host will not be sent out if the master host is in a DOWN state.
Parameter name: notification_failure_criteria
Required: no
You do not have the required permissions to view the files attached to this post.
Be sure to check out our Knowledgebase for helpful articles and solutions!