You have the option to associate multiple dependent devices across managed servers. Dependencies determine the health availability of a Monitor. This includes dependent parameters of the Monitor based on which the severity of the health and availability are determined. By configuring dependencies, you can specify whether the health or availability depends on all or few dependencies. The severity is also determined by order of severity which is given below:
For example, If there are 9 dependencies in a Monitor Group where three are critical, three are warning, and three are clear and the severity of Health of Monitor Group is based on any three selected dependencies, then the severity will be Critical as per the order of severity.
To configure dependencies for the Monitor, do the following steps:
Configuring Alarm Rules for Monitors / Monitor Groups:
By configuring Alarm Rules, you can specify how the health or availability depends on the constituent Monitors in that Monitor Group. For eg., using Alarm Rules, you can say Health of the Monitor Group is Critical if the health of any two monitors in the monitor group is critical or Availability of the Monitor Group is Critical if health of any one of the monitors is critical.
To configure alarm rules for the Monitor Group, do the following steps:
For Availability Alarm Rule
Dependent Device - Monitor Group can have a device where Child Monitors Availability status will depend on the Device Availability.
For Health Alarm Rule
Dependent Device - Monitor Group can have a device where Child Monitors Availability status will depend on the Device Availability.
You have the option of setting any number of rules. For eg., it can be Monitor Group's Availability is down if any one of the monitor's availability is down or if the health of any one of the monitor is critical. Likewise, you can have your customized set of Alarm Rules.
You can configure a dependent device in such a manner that if the availability of the dependent device is down, the concerned Monitors/Monitor Group's availability will be down. You can configure the dependent device for a Monitor Group or individual monitor to suppress false downtime alarms caused by the dependent device being down.
Configuring Dependent Device
To configure dependent device for the Monitor Group, do the following steps:
Here are a few scenarios of monitor dependencies and the state of the parent monitorafter adding the dependency:
Monitor 1 | Monitor 2 | State of monitor 1 After Adding monitor 2 as Dependency |
---|---|---|
Down | Down | Down - As both Monitor 1 and Monitor 2 are down. |
Down | Up | Down - As Monitor 1 is down. |
Up | Down | Up |
Up | Up | Up |
You can configure a dependent monitor group in such a manner that if the availability or health of that dependent monitor group is affected, the corresponding monitor group's availability or health will also be affected.
Configuring a Dependent Monitor Group
To configure a dependent Monitor Group, do the following steps:
Cyclic Dependencies: Cyclic Dependencies sometimes arise when multiple dependent devices are associated across managed servers to form a loop, resulting in infinite recursions. As it is a rather tedious task to track errors caused by circular dependencies, it is important to consider how your device dependencies are configured and to try to keep all of the dependencies acyclic. This means that if device A depends on device B, and device B depends on device C, we don’t want device C to depend on device A.
Here are a few scenarios of monitor dependencies and the state of the parent group after adding the dependency:
Monitor Group 1 | Monitor Group 2 | State of group 1 After Adding Group 2 as Dependency |
---|---|---|
Down | Down | Down - As both Group 1 and Group 2 are down. |
Down | Up | Down - As Group 1 is down. |
Up | Down | Up |
Up | Up | Up |
Suppress Alert for Dependent Monitor Groups
Users can suppress Alerts For Dependent Monitor Groups. The suppress alert feature works the same for both Dependent Monitor and Dependent Monitor Group. If a user chooses to suppress alerts for a Dependent Monitor then alerts are suppressed for the parent Monitor Group too. Here are possible scenarios:
Monitor Group 1 | Monitor Group 2 | Monitor 1 | Suppress Alerts ? | State of Group 1 After Adding Dependency of Both Group 2 and Monitor 1 |
---|---|---|---|---|
Down | Down | Down | No | Down - As all Group 1, Group 2 and Monitor 1 are down |
Down | Down | Up | No | Down - As Group 1 and Group 2 are down |
Down | Up | Down | No | Down - As Group 1 and Monitor 1 are down |
Down | Up | Up | No | Down - As Group 1 is down. |
Up | Down | Down | No | Up |
Up | Down | Up | No | Up |
Up | Up | Down | No | Up |
Up | Up | Up | No | Up |
Down | Down | Down | Yes | Health-Critical - As all Group 1, Group 2 and Monitor 1 are down. |
Availability-UP - Alert is Cleared due to Dependent Monitor Configuration | ||||
Down | Down | Up | Yes | Health-Critical - As Group 1 and Group 2 are down. |
Availability-UP - Alert is Cleared due to Dependent Monitor Configuration | ||||
Down | Up | Down | Yes | Health-Critical - As Group 1 and Monitor 1 are down |
Availability-UP - Alert is Cleared due to Dependent Monitor Configuration | ||||
Down | Up | Up | Yes | Down - As Group 1 is down. |
Up | Down | Down | Yes | Up |
Up | Down | Up | Yes | Up |
Up | Up | Down | Yes | Up |
Up | Up | Up | Yes | Up |