Assign Action Profile
The Severity tab enables you to assign an action profile to a service container. The action profile is triggered when the service container changes to a specified severity status. See Action Profiles for more information.
Severity Determined by
The severity status of a container can be one of four values:
The severity status is determined using one of the following methods:
Rule-based - Calculating the severity of the container. The rule is based on the percentage of devices or tests that have reached a selected severity value. Traverse requires that you specify rules from "worst to best". Select the worst condition (Critical) in the first Device/Test severity drop-down menu, followed by Warning in the second drop-down menu, and then OK in the last drop-down menu. The rule-based approach is most useful for redundant or clustered devices, such as behind a load balancer.
Severity Affected by Message Events
Example
Assume an e-commerce service with a cluster of web servers in the front, connected via two redundant routers to a remote location housing a database. Since containers support nesting, you can model the above using multiple nested containers such as:
If any of the three components in the eCommerce container goes into a non-OK condition, the top level eCommerce container will also change its state in real time.