eG Help

To optimize accesses to the database, the eG manager uses connection pooling. By using a pre-established set of connections and multiplexing requests over these connections, the eG manager ensures that individual connections are not established and closed for each request. Using the eG administrative interface, an administrator can configure the initial number of connections in the pool and the maximum number of connections. If the pool has not been configured with enough connections, then the eG manager may not be able to connect to the database to store the critical performance metrics reported by the eG agents. Therefore, to be able to judge the adequacy of this configuration, you need to understand how the eG manager uses the connection pool.

This test sheds light on the usage of the connection pool by the eG manager, and indicates whether/not the connection pool has been rightly sized.

Measurement	Description	Measurement Unit	Interpretation
Initial_connections	Indicates the number of initial connections allocated to the pool.	Number	Both these parameters can be configured using the DATABASE SETTINGS page that appears when the Configure -> Data Management -> Database Settings menu sequence is followed in the eG administrative interface. Consider increasing the number of connections in the connection pool as the number of components monitored or the number of users accessing the system increases.
Max_connections	Indicates the maximum number of database connections that the eG manager can use from the pool.	Number
Used_connections	Indicates the number of connections currently used by the eG manager.	Number	If the value of this measure grows dangerously close to the value of the Maximum connections measure, it indicates that the pool is rapidly running out of connections. In such a case, you can use the detailed diagnosis of this measure to know which classes are currently utilizing the database connections, and how many connections have been used per class. Classes that are over-utilizing database connections can thus be identified, and the reasons for the same can be determined.
Free_connections	Indicates the time taken for connections to time out.	Number	A low value for this measure is a cause for concern, as it indicates that the connection pool does not have enough free connections. This could be owing to an increase in the number of components monitored or the number of users accessing the systems. You may hence want to consider fine-tuning the Initial Connections and Maximum Connections parameters (using the eG administrative interface), so that the pool is sufficiently sized to handle the increase in workload.
Connection_timeout	Indicates the time taken for connections to time out.	Secs	By carefully observing the value for this measure over time, you can figure out the maximum ideal time for which a connection should stay alive.
Total_connections	Indicates the total number of connections in the pool.	Number
Connections_waiting	Indicates the number of connections that are currently waiting to be closed on the eG manager.	Number	Ideally, the value of this measure should be low. A very high value of this measure is a cause for concern as it indicates that too many connections to the database are currently open and are waiting to be closed, but are unable to close owing to certain issues. Besides unnecessarily consuming connections from the pool and causing a paucity of connections in the pool, these waiting connections, if allowed to increase, can even cause the manager to restart.