This example demonstrate how rule based severity in a container can be used to monitor two tests on the same device. One test is active when the primary circuit (in this example; in other examples it may be the primary SQL server service in a cluster, etc.) is active - and the other test (usually representing the inactive or backup) is inactive. At any given time, if one test is OK in Traverse (be it the primary or the backup), the functionality is still available. However, if both go Critical, then the functionality is not available and the customer would like to receive notification of this.
Create a Test Based Container with Rule Based Severity
Creating a Test Based Container
1. Navigate to Administration > Containers > Create a Service Container
2. Enter a unique container name in the field at the top of the middle Container Configuration panel.
3. Select the Contains: Tests option.
4. In the right hand panel, enter one or more search qualifiers to search for the
names of the relevant tests. Select the tests and click Add.
Refer to the documentation for more information on Containers
Configuring Container Severity
1. Click on the SeverityTab
2. Select the Rule-based option
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.
Refer to the documentation for more information on Container Rules