An External Test is one that is run outside of Traverse (by a stand-alone script, for example). The test result is inserted into Traverse via the External Data Feed (EDF) and aggregated as though Traverse had collected it. Although the test itself is not run by Traverse, by creating an External Test, you determine how test results will be processed after they are received via EDF.
For more information on implementing external tests, see the Traverse Developer Guide & API Reference.
Creating an External Test
Field |
Description |
Test Units |
The units in which test results are displayed. |
Maximum Value |
Maximum possible return value for this test. You can generally ignore this unless you are using the test result to calculate a percentage of a whole. In that case, enter the value of the whole in this field. For example, if a test returns the number of MB available on a disk and you want to calculate the percentage of the disk's storage space that is available, enter the disk's total storage space in this field. |
Result Multiplier |
A number by which the test result is multiplied. If a test returns a number of bytes, for example, you can use a Result Multiplier of 8 to convert the result to bits. |
Alarm After Inactivity |
Number of minutes after which the DGE will mark stale test results as FAIL. The check is performed only if the DGE has received at least one test result since it was created. Use this to provide notification if no new results have been received for an external test. |
Post Processing Directive |
The computation applied to the test result after it has been multiplied by the Result Multiplier. Options include:
|
As test value rises, severity: |
Specify the relationship between test value and severity. Options include:
|