The Dependency List describes all resources that a Group requires to function correctly.
Examples of resources that Groups are Dependent upon to function:
- Router
- UPS device
- Authentication Server
- Remote Access Server
- Stable path to another network
In the event that resources such as those listed above fail, dependencies can greatly reduce the number of redundant notifications as illustrated below:
- If a critical resource in the Dependency list becomes unavailable.
- All Members (monitors) of the group will become unavailable because they depend on the resource.
- Each monitor that becomes unavailable is checked to see if Alerts should be triggered.
- Alerts will be sent out for the critical resource that the group depends on to function. No Alerts will be sent out for the dependant monitors.
To make a monitor a Dependency, check the dependency checkbox adjacent to its name.