Update Test

1. Navigate to Administration > Tests. The Test Management page displays.
2. Click the edit icon on any row to display the Update Test page for that test.

The following is a list of the most common properties you can set by updating a single test using the Update Test page. See standard test parameters for additional properties. You'll notice for SNMP and WMI in particular, that Traverse has already set these to default values for the standard tests you have created.

• Test Name - Populated automatically when the test is provisioned by Network Discovery.
• Test interval - Options vary depending on the test.
• Adaptive Threshold - See Adaptive Time Based Thresholds.
• Warning Threshold - Specifies the threshold that causes a test to change to a WARNING state.
• Critical Threshold - Specifies the threshold that causes a test to change to a CRITICAL state.
• Unit - Options vary depending on the test.
• Flap Prevention Wait Cycles - Sets the number of cycles to show the TRANSIENT state when a test changes states. For example, if flap-prevention cycle is configured to be 2, and a ping test is configured for 3 minute interval, when the ping test switches from OK state to WARNING, until the test remains in the new state for 2 additional cycles (6 min), on the web application the test will be shown in TRANSIENT state.
• Schedule - Selecting a schedule limits testing by time of day or by weekday.
• Action Profile - An action profile with an asterisk indicates a default action profile created by an administrator.
• As test value rises, severity - Specify the relationship between test value and severity.
  • Auto - Severity is based on the Warning and Critical thresholds for this test. If the Critical threshold is higher, as test value rises, severity ascends. If the Warning threshold is higher, as test value rises, severity descends.
  • Ascends - As the value of the test result rises, severity rises.
  • Descends - As the value of the test result rises, severity falls.
  • Discrete - Specify a list of integers or ranges of numbers using the syntax: 1,3,5,10-25. Specify different values for warning and critical. Any returned value that does not match a value in either list means the device is OK.
  • Bidirectional - Specify a range of numbers for each threshold. If the value crosses either of these two boundaries of the range, severity is set to Warning or Critical.
• Post Processing Directive - The computation applied to the test result after it has been multiplied by the Result Multiplier.
  • Percent - Current polled value / Maximum Value (e.g., current polled value represents 20% of total disk space).
  • Delta - current polled value - last polled value (for example, 3 MB of disk space used since last poll).
  • Delta Percent - (Current polled value - last polled value) / Maximum Value (e.g., the difference between the current value and the last value represents 2% of total disk space).
  • Rate - Delta / time between polls (e.g., rate of disk usage is 3 MB in 5 minutes).
  • Rate Percent - Percentage change since the last poll (e.g., rate of change measured as a percentage of the whole is 2% of total disk space in 5 minutes).
  • Rate Invert - Perform a rate calculation (2 consecutive poll, measure delta, divide by time) and then subtract the value from the configured maximum. Similar to Reverse Percent, but does not perform the % calculation.
  • Reverse Percent - The difference between 100% and the percentage represented by the last polled value (e.g., last polled value for a disk usage test represents 20% of total disk space, so the reverse percent is 80%, which is the amount of free space).
  • HexString to Long - Poll an expected hexadecimal (base 16) value to convert it to base 10. For example the hexadecimal value 1A is converted to 26. Supports positive values only.
  • TimeTicks - Divide an expected timeticks value by 100 to convert it to seconds.
  • None - Polled value is not processed in any way.
• Suspend/Resume - When tests are suspended, polling and data collection for those tests are suspended. All actions and notifications associated with suspended tests are not generated. Time is not included in total downtime reports since it is considered a planned outage. Devices can also be suspended. When you resume a suspended test, the test is rescheduled to run on the monitor. If you visit the Test Summary page for the device that the test is on, you may see an unknown (question mark) icon in the status column. This indicates that the test has been rescheduled, but that its status is not yet known because it hasn't yet run. After the test runs, the unknown icon is replaced with the appropriate status icon.