Tests Test
This test auto-discovers the tests that report the data to the target eG agent and reports the number of components for which each test was executed by the eG agent and the time duration(maximum/minimum/average) taken for test execution. In addition, this test throws the spotlight on the tester threads that are available for starting the execution of each test. Using this test, administrators can easily figure out how well the tester threads were utilized for executing each test.
Target of the test : The eG Agent
Agent deploying the test : An internal agent
Outputs of the test : One set of results for each Test from which metrics are collected by the target eG Agent being monitored.
Parameter | Description |
---|---|
Test period |
How often should the test be executed . |
Host |
The host for which the test is to be configured. |
Port |
The port number at which the specified host listens. By default, this is NULL. |
Detailed Diagnosis |
To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:
|
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Total components managed by this agent |
Indicates the total number of components for which this test was executed and metrics collected from this test by the target eG agent. |
Number |
|
Minimum frequency |
Indicates the minimum time taken to execute this test.
|
Mins |
The value of this measure could be between 4.5 to 5.5 minutes. A value higher/lower than the specified limit is a cause of concern. |
Maximum frequency |
Indicates the maximum time taken to execute this test. |
Mins |
The value of this measure could be between 4.5 to 5.5 minutes. A value higher/lower than the specified limit is a cause of concern. The detailed diagnosis of this measure lists the components for which this test executes with the maximum time duration. |
Average frequency |
Indicates the average time taken to execute this test. |
Mins |
|
Test reporting ratio |
Indicates how well the test was performing i.e., how well the test was reporting metrics to the target eG agent, in terms of percentage. |
Percentage |
A value greater than 100 for this measure indicates that the test was not executing in the configured measurement period. It may also indicate that the test took too long to execute. |
Tester busy |
Indicates the percentage of time the tester threads configured for this test were busy. |
Percentage |
Tester threads on the eG agent are responsible for starting the execution of the test and collecting appropriate metrics. A low value for this measure indicates that more components can be managed and monitored by the eG agent. A value close to 100 is a cause of concern. |
Total testers |
Indicates the total number of tester threads that were currently available for executing this test. |
Number |
|
Running testers |
Indicates the total number of tester threads that were currently executing this test. |
Number |
|
Tester Utilization |
Indicates the percentage of tester threads utilized by this test. |
Percentage |
A low value is desired for this measure. If the value of this measure is close to 100%, it could indicate that the test is about to utilize its entire thread pool. Under such circumstances, you can consider increasing the maximum number of threads that the test can spawn for execution. |