eG Monitoring
 

Measures reported by EgTestOverviewTest

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 executing 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 executing the test. Using this test, administrators can easily figure out how well the tester threads are utilized in executing each test.

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
Total_Components Indicates the total number of components for which this test executed and reported metrics to the eG agent. Number  
Test_Min_Freq 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.
Test_Max_Freq 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.
Test_avg_Freq Indicates the average time taken to execute this test. Mins  
Test_Report_Ratio Indicates how well the test is performing i.e., how well the test is reporting metrics, in terms of percentage. Percentage A value greater than 100 for thismeausre indicates that the test was not eexecuting 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 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_tester Indicates the total number of tester threads that were currently available for executing this test. Number  
Total_Run Indicates the total number of tester threads that were currently executing this test. Number The threads play a major role is starting the execution of the test.
Total_Util 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.