eG Monitoring
 

Measures reported by EgTrendManagerTest

The eG Trend manager process uses the raw measurement data in the eG database to compute hourly, daily, weekly, and monthly summaries and performance averages, and stores these computations in trend tables. Users to the eG monitoring and reporting consoles can query the data in the trend tables to generate trend graphs and reports. These graphs/reports enable administrators to clearly understand the historical trends in performance, on the basis of which they can accurately predict future performance and effectively plan the future capacity of the environment. Using this test, you can understand how efficient the trend manager process is.

This test reports the current status of this process, points you to trend computation failures and where they occurred, and reveals slowdowns in trend computation (if any).

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
Trend_Status Indicates the current status of the trend manager process.   The values that this measure reports and the numeric values that correspond to them have been discussed in the table below:

Measure Value Numeric Value
Running 0
Sleeping 1
Error 2
Not Started 3
Interrupted 4

Note:

By default, this measure reports the Measure Values listed in the table above to indicate the current status of the trend manager process. The graph of this measure however, represents the same using the numeric equivalents only.
Time_Taken_For_Trend Indicates the total time taken by the trend manager process to perform trend computations. Minutes Ideally, the value of this measure should be low. A steady rise in this measure value is a cause for concern, as it indicates that the trend manager is taking too long to compute trends. This can happen if there are too many components, tests, and measurements for which trends need to be computed.
Trend_Success_Tests Indicates the number of tests for which trends were computed successfully. Number You can use the detailed diagnosis of this measure to know the tests for which the trend data has been successfully computed.
Trend_Failed_Tests Indicates the number of tests for which trend computation failed. Number The value 0 is desired for this measure. Any non-zero value is indicative of a trending failure. In this case, you can use the detailed diagnosis of this measure to identify those tests for which trend computation failed and investigate the reason why. Without trend data, users may not be able to generate useful trend graphs and reports; in the absence of trend reports, capacity plans cannot be drawn accurately.
Time_Since_Last_Trend Indicates the elapsed time since the last trend computation. Minutes Typically, trending is scheduled to take place at the end of every day. By carefully observing the values reported by this measure, you can easily find out when a scheduled trend computation cycle was missed.
Is_Trend_Seperate_Proc Indicates whether/not the trend manager is running as a separate process.   The eG manager runs as a Java process. The maximum heap memory that can be allocated to a 32-bit eG manager process is limited to 1.5 GB. The maximum heap memory allocation to a 64-bit eG manager process on the other hand, is limited to 3 GB.

Even if the physical server on which the eG manager is installed has more memory, since it is a single Java process, the eG manager cannot exploit the additional memory available on the server. To overcome this limitation, in eG Enterprise, the critical eG manager functions such as email alert management, threshold computation, trending, and database cleanup activities can all be run as separate Java processes (i.e., in addition to the core eG manager process).

Removing these key functions from the core eG manager process makes additional memory available for the core eG manager functions including data reception and analysis, alarm correlation, and web-based access and reporting. This reconfiguration of the eG manager into separate Java processes allows the eG manager to make better utilization of available server hardware resources and thereby offers enhanced scalability. In turn, this allows customers to get more leverage from their existing investment in the hardware that hosts the eG manager.

If cleanup has been configured to run as a separate Java process, then the value of this measure will be Yes. If not, then this measure reports the value No.

The numeric values that correspond to the measure values above are as follows:

Measure Value Numeric Value
Yes 1
No 0

Note:

By default, this measure reports the Measure Values listed in the table above to indicate whether/not the trend manager runs as a separate Java process. The graph of this measure however, represents the same using the numeric equivalents only.

Has_Trend_Run_Today Indicates whether/not trend has run on this day.   Typically, trending is scheduled to take place at the end of every day. If the value of this measure is Yes, it indicates that trending has run today. On the other hand, if this measure reports the value No, it indicates that trending is yet to run for that day or has not run at all.

The numeric values that correspond to the measure values above are as follows:

Measure Value Numeric Value
Yes 1
No 0

Note:

By default, this measure reports the Measure Values listed in the table above to indicate whether/not trending has run today. The graph of this measure however, represents the same using the numeric equivalents only.

Slow_Trend_Tests Indicates the number of tests for which trend data computation was slow. Number Use the detailed diagnosis of this measure to know the tests for which the trend data computation was slow.
Trend_Run_Days Indicates the number of days since the trend manager was started. Days  
Time_Taken_For_Reporter_Data Indicates the time taken by the trend manager to perform trend computations for historical state data. Minutes  
Time_Taken_For_Schedule_Report Indicates the total time taken by the trend manager to perform trend computations for schedule reports and send the same. Minutes