This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Dependency aware Alert examples

Hi guys,

Could anyone please share screenshots of their trigger condition for an alert that is suited to mute Down alerts on Child objects that are down?

I have a dependency where a router is the parent and a group is the child. I only wish to receive alerts when the router is down and suppress the hundreds of alerts I would get when the group members are down. Any help greatly appreciated.

Parents
  • This doesn't impact the alert definition as the related entity never goes into a 'Down' state when its parent is down. Instead, the entity goes into an 'Unreachable' status. So unless you've configured your alerts to trigger when the status is anything other than 'up', you won't be alerted when an entity is 'unreachable' (parent is down) rather than 'down' (parent is up, child is down).

  • Hi aLTeReGo

    Thanks for the swift reply. There's something I am missing here for sure, so I hope you can explain it further for me.

    This is what I have done to test the functionality:

    I've created a static group that includes some nodes that are Up and confirmed that it works as it should.

    I then create a manual dependency where I selected a random node that was down, set it to be the Parent and selected the static group that includes Up nodes to be the Child.

    At this point, I was expecting the Up nodes from the group to have an Unreachable status but that wasn't the case. Reviewing the nodes in Summary views and even their respective Details view still showed them as being Up.

    Nowhere was I able to see the Unreachable status.

    Was my test procedure configured wrong or could there be an issue with my installation?

    Also, does having automatic dependencies enabled break this test, and if so, does that mean that Automatic Dependencies must not be enabled if you want something like this to work?

Reply
  • Hi aLTeReGo

    Thanks for the swift reply. There's something I am missing here for sure, so I hope you can explain it further for me.

    This is what I have done to test the functionality:

    I've created a static group that includes some nodes that are Up and confirmed that it works as it should.

    I then create a manual dependency where I selected a random node that was down, set it to be the Parent and selected the static group that includes Up nodes to be the Child.

    At this point, I was expecting the Up nodes from the group to have an Unreachable status but that wasn't the case. Reviewing the nodes in Summary views and even their respective Details view still showed them as being Up.

    Nowhere was I able to see the Unreachable status.

    Was my test procedure configured wrong or could there be an issue with my installation?

    Also, does having automatic dependencies enabled break this test, and if so, does that mean that Automatic Dependencies must not be enabled if you want something like this to work?

Children