Local dependencies

Dependencies prevent multiple alarms from being triggered when a single condition exists that forces all related monitors to enter an alarm state. The parent monitor in a dependency tree is called the root monitor. Only local dependencies are supported, meaning root and dependent monitors must belong to the same object. Dependent monitors can still enter an alarm state independently, but only if their root monitor is not in an alarm state.

For example, if connection to an object is lost, then the object's Ping monitor will enter an alarm state, along with many other monitors that might be specified for this same object. Designating the Ping monitor as the root monitor prevents those other monitors from entering an alarm state as well. This prevents being notified multiple times for the same alert condition.

Once a dependency is created, you can identify local dependencies on the Monitor List page. Dependent monitors display as an indented tree of dashed lines. The Next test column also identifies the monitor as a member of a local dependency tree. Dependent monitors display an orange status icon instead of a red status icon when the parent monitor enters an alarm state.

Creating Local Dependencies

1. Click the Properties option on the Object information page.
2. Select a Root monitor.
   • This is the monitor which all other monitors in this object will be dependent on.
   • If this is a template, the dependency tree will be inherited.

Creating Local Dependencies using Network Discovery

1. Click the Tools > Network discovery > Start new option.
2. Wait for Network discovery to return a list of discovered machines
3. Select one or more discovered machines.
4. Click Add object.
5. Click the Create dependency checkbox. This only works if one of the monitors being created automatically as the object is added is a Ping monitor.