Thanks a lot for coming back to me, Steve Ebersole, and everyone. I understood there's been a problem with the issue notifications.

Speaking for Vibur, what I meant under "advanced performance monitoring" is from application to database interactions point of view, will explain. Vibur detects and logs (for the logging below) on the app side any SQL queries which execution has taken more than a given time limit; any calls to DataSource.getConnection() that have taken longer than a given limit (this limit is different then the getConnection timeout limit); any SQL queries which execution has generated/retrieved a ResultSet that is longer than a given limit. The logged data/events either finish in a log file via slf4j, or goes back to the calling application via an interface which the application has injected in the connection pool. The logs can be later investigated for performance issues and actions can be taken based on them. I know that some of these logs can be obtained on SQL server side, and I know about libraries such as log4jdbc, however, given that all these "performance" data is readily available at the connection pool library, I couldn't see why the pool won't take care of logging it.

The online documentation describes the above Vibur features in details, however please note that as I released a new version of Vibur yesterday, the online docs are slightly out-of-date atm (nothing major) - I'll bring them up-to-date over the next few days.

Vibur is not currently exposing metrics via dropwizard/codehale, but this is something which I can consider for next releases. Metrics wise, Vibur provides several Connection lifecycle and method invocation hooks through which it can notify the application about various events like physical JDBC Connection establishing or closing, the times taken for these, etc. And then the application can take care of providing/creating metrics based on these notifications; in fact, that is what I recently implemented in a company's project.

And just to reconfirm, I'm happy to help now with the initial integration of Vibur with Hibernate, as well as I'm happy to stay involved in future and help with what might be needed later. Said all that, what will be the next step that we're looking at? How we're going to implement this integration?