Connection pool monitoring
The FlexyPool library adds metrics and flexible strategies to a given Connection Pool, allowing it to resize on demand. This is very handy since most connection pools offer a limited set of dynamic configuration strategies.
Features
- multiple environment options
- Stand-alone (Spring, Guice)
- Java EE
- extensive connection pool support
- statistics support
- concurrent connections histogram
- concurrent connection requests histogram
- data source connection acquiring time histogram
- connection lease time histogram
- maximum pool size histogram
- total connection acquiring time histogram
- overflow pool size histogram
- retries attempts histogram
Tutorials
- The anatomy of Connection Pooling
- FlexyPool, reactive connection pooling
- Professional connection pool sizing
- The simple scalability equation
- How to monitor a Java EE DataSource
- How does FlexyPool support both Connection proxies and decorators
- FlexyPool 2 has been released
Makes sense. Logging all query executions can let you know how much time is spent by executing statements. But you should also take into consideration the fetching phase as well. You could add a timer in your data access logic to measure the duration of the whole data execution.
But, the connection acquisition is not correlated to the SQL query that comes afterwards. These are two separate mechanisms. You could print the query execution time with datasource-proxy or p6spy, and aggregate all data using ElasticSearch and view it in Kibana. You might want to print the threadId, to make sure that all logs get correlated by thread and time.
You can always use the generic DataSource connection pool that was designed for Java EE. It should work with any DataSource implementation and it will collect all metrics for you. You won;t be able to adjust the pool size using overflow buffer, that being the only limitation.
If you want to develop a new adaptor, it’s fairly simple. You just have to add a new Maven module, set the Maven dependency and then provide the Adaptor implementation which can set the max pool size and translate the connection acquisition request timeout exception. You can take any other adaptor module as an example, it’s really straight forward.