The reason for this dependency is that when this device fails, ipMonitor will limit alerts to the monitor defined as the dependency
rather than triggering alerts for every member monitor.
This is by design. The reasons are :
1.) Minimizes the number of redundant alerts.
2.) Helps isolate the root cause of the problem.
3.) Prevents configured Recovery Alerts from attempting to restart services and
applications if such an action is not required.
Thank you for the clarification.
One last question, what is the correct way to set a dependency for a group of systems at a remote site?
State Group - City Group - Building Group - Floor Group - Systems on that floor.
I have multiple systems and I would like the alarm to roll up to the ( State ) view if a system alarms. Is this automatically done by group association or do I need to setup dependencies all the way down? Also for the floor group how do i set the router / switch as a dependency for all the systems.
My apologies if this seems like a no brainer ( and I do think I understand what to do ) however, I am setting this system up for the first time and I would like to get it right.