Apply Dependency in Icinga Director doesnt work

Icinga Web Modules Icinga Director
1

Hello,

we are trying to do Parent-Child Dependencies on our Routers, so we dont get spammed with Notification when the Core-Router is going down.

We have all our configuration in Icinga Director.
Here is what the config is looking like:

Parent: DSL-Router:

image
image773×486 14.9 KB

Child: Switch

image
image777×553 17.3 KB

With the custom var “parent” filled with the hostname of the Parent.

The Apply-Dependency:

image
image796×683 17 KB

This configuration is not working, when the parent and child goes offline, both still send an email notification. We want only a notification from the parent.
I checked the documentation in the icinga2 config and couldnt find any error in our configuration. I tested also, if the apply Rule is triggering. I created a new Hostgroup apply on “host.vars.parent” == DSL-Router and the Child-Switch was in that hostgroup. So its applying correctly.

Does anyone have any idea on what is wrong here?
Thank You really much!

Cherry

2

Hello,
Could you share what is defined under “Related Objects” in the Dependency? And/or the Preview of the dependency?
Thank you,
Jean

3

oh sorry:

image
image793×780 18.6 KB

Config in /var/lib/icinga2/api/zones/icinga.domain.com/director/dependency_apply.conf

apply Dependency "Parent-Child" to Host {
    import "Parent Firewall"

    parent_host_name = "DSL-Router"
    disable_checks = true
    disable_notifications = true
    ignore_soft_states = true
    assign where host.vars.parent == "DSL-Router"
    states = [ Up ]
}
4

Hello,
The configuration looks fine.
In what order are your notifications triggered? If you notice that the notifications for the children are triggered first, you may want to delay them, so that Icinga has the time to assess that the parent has reached the Down status, which will activate the dependency, marking the children as “Unreachable”, which in turn will have the effect of not sending the notification for the children (even if their own Down status was reached before the parent’s).
Hoping this is clear,
Jean

5

Hello Jean,

we simulated multiple network failures by changing the IP-Adress of the Router and the Switch on the same time. We get the notification of the Router first and 2-3 Minutes after that we will receive the notification of the switch.

6

Please show the configuration of the hosts from the preview tab and check for typos there.
Normally when the dependency is configured correctly the parent state turns critical (or warn) and the child’s state turns unknown (to Show the dependency) with not-ok results

7

Parent:

object Host "DSL-Router" {
    import "general"

    display_name = "DSL-Router"
    address = "192.168.172.254"
}

Child:

object Host "Switch-Child" {
    import "general"

    display_name = "Switch-Child"
    address = "192.191.222.192"
    vars.parent = "DSL-Router"
}

The variable “parent”:

image
image835×556 15.4 KB

8

Someone has any Idea? We cannot find any Error in the configuration.

9

Should work from what I can see.
Can you try icinga2 object list --type dependency ? This should show a Dependency object for every child.

10

Thank You very much!
This was resulting to solve the problem.
After i tried Your cli command, this was shown:

warning/cli: This data is 324 days, 4 hours and 36 minutes older than the last Icinga config (re)load. It may be outdated. Consider running ‘icinga2 daemon -C --dump-objects’ first.

After i did ‘icinga2 daemon -C --dump-objects’ the Dependency looks like its working! What can cause the reason, Icinga is loading outdated configs?

11

@Cherry Slight misunderstanding here. Icinga 2 doesn dump the configuration into files at every reload anymore (since a few versions), but the icinga2 object list command reads from those files (legacy stuff I guess).
Therefore you have to tell Icinga 2 to dump the config first to view it, but it was already running with that configuration.

If you can see the dependencies there, they are there (and active), the question is now why it does not yet work as intented (or does it by now)?

12

Thank You for the explanation!

The dependency is working now. We will test it in the next days and simulate a network failure. @lorenz @jeanm @Tqnsls thanks for the help!

Best regards
Cherry