Default thresholds define WARNING and CRITICAL status for end user tests. Warning thresholds are usually selected to provide early warning of potential problems or to identify trends that approach critical status. Critical thresholds are usually set at levels that warn of impending SLA violations or device failures. If they wish, administrators can use the Default Action Thresholds and Actions page to modify the default Traverse thresholds used to trigger an action profile for a combination of user-class and test types.
Note: In general, default threshold settings are established when a user-class is created and should not be changed.
Note: Default Action Thresholds and Actions settings apply only to new tests. Existing tests are not affected by user-class default thresholds. Use the BVE API to make changes to existing tests.
Configuring Default Thresholds/Action Profiles for a User-Class
Field |
Description |
Delete Settings |
Select this check box to delete the test parameters for all listed tests. You can also select the check box associated to individual tests to delete parameters for that test. |
Discover Test |
Select this check box to discover all tests for all all listed categories. You can also select the check box associated to individual tests to discover that test. Clear the check box to prevent discovery of the test. |
Warning Threshold |
The test result that causes the test's status to change to WARNING. |
Critical Threshold |
The test result that causes the test's status to change to CRITICAL. |
Severity Behavior with Value |
Specify the relationship between test value and severity. Options include:
|
User Class Action |
The default action [rofile that is applied to tests of this type that are created by end users from this user class. These actions profiles are for notification of end users (not administrators) and always email the recipient specified for the department of the end user who creates the test. |