I'm in the process of setting up dependencies for each device and also routers for remote sites that the devices will be dependent upon.
First....a suggestion - When setting up a device or group dependency, I'd like the system to automatically assume I'm interested in the monitors currently assigned to the device or group I'm working with. Right now, the filter assumes whatever the previous filter was set as.
There is already an easy option to use a "previous" filter in the event that function is needed. (ie. Last filter used or previously saved filter.)
Now the question - Is there an easier way of setting up the dependencies? Currently, I'm selecting the device/group and using the "add dependency" drop down for each device/group.
Another question, though I'll have tested it shortly. How is the system going to react when I create a group of devices by geographic location, set the router monitor as a dependency for the group, where each device in the group already has it's own dependency (ping)?
My first assumption is to make sure the timing/warnings are set at a more frequent interval for the router than the device ping...and the ping at a more frequent interval than the other monitors.
FWIW - I really like the way the dependencies show up on the NOC view. Even though we know the other monitors are technically "down", it doesn't generate more confusion (and red lines) for those looking at the screen and making phone calls to the on-call.