Been thinking about this a bit more....
Maybe make it so we can set a particular monitor as a dependency of many in reverse. In essence, "add existing monitors/devices" to the dependency monitor.
Rather than adding the dependency to the group, you add the "group/device/monitor" to the dependency. As is done with alerts. We can select an alert, then add whatever we want to it.
1 of 1 people found this helpful
Essentially you want to organize your Monitors and Devices based on the trip taken to get to these. For example, let us say you are monitoring the Bandwidth and the Drive Space on a Mail server in a specific office and these tests depend on a few appliances such as a Gateway and a Switch. In order to configure your dependencies accordingly, you would first create a group for this office, then a subgroup for the Mail Server Device. You would then create a Ping Monitor to the Gateway and a Ping Monitor to the Switch (if managed). As Monitors cannot exist outside of Devices, you would need to put these into Devices. Add these Devices and the Mail server group directly into the Office group. Then add the Mail Server device to the mail server group and within the Device, in addition to the bandwidth and drive space Monitors, add a Ping Monitor and make it a dependency for the Device. Now add the Ping Monitor to the Switch as a dependency to the mail server group and add the Gateway Ping Monitor as a Dependency to the Office group. As a result, if a Dependency fails, anything in that group will be supressed from Alerting. Here's a screenshot that should speak better than words.
Hope this helps organise your Dependencies as needed.
Thanks for the reply. Let's see if I have this right....(the picture is a welcome addition :~) )
A dependency will effect the sub-groups below it and the one it's contained within.
In application, if the dependency monitor triggers within a group, all groups nested within, including the group that contains the dependency, will not trigger other alerts.
In your scenario....
If the gateway ping fails, only the gateway ping alert is triggered. All others are suppressed.
If the switch ping fails, the monitors of the mail server are suppressed.
At the mail device level, the ping dictates whether the other monitors alert.
This being my understanding, if correct, it sure would be nice to be able to set a dependency on a smart group.
This is currently not possible, however, you can group the SmartGroups within a main group and make the main group dependent on one or more Monitors. I realize this is not ideal, but it brings you very close to what you need.
Yes...creating smart groups within the main group would certainly do the trick. It will allow additions of devices/monitors to be automatically dependent upon the router monitor regardless of where the device is originally created.
Thanks very much for your time and knowledge of this.