There are four vRealize Hyperic alerts that relate to JDBC connection monitoring. You can enable log tracking of the alerts to monitor JDBC connections to a database and the status of JDBC queries.
About this task
vRealize Hyperic includes the
SpringSource tc Runtime 7.0 Tomcat JDBC Connection Pool Global service that represents any high-concurrency Tomcat JDBC data sources you might have configured for your tc Runtime instance. This service monitors the health of the data source, such as whether its connection to the database has failed or was abandoned, and whether the JDBC queries that clients execute are taking too long. vRealize Hyperic creates this service when you create a new Tomcat JDBC data source. There is one instance of a service exists for each data source.
There are four vRealize Hyperic alerts that are associated with this diagnostic feature. They are triggered as follows:
JDBC Connection Failed
A specific high-concurrency JDBC connection that uses a configured datasource failed.
JDBC Connection Abandoned
A specific high-concurrency JDBC connection that uses a configured datasource is abandoned by the database server.
JDBC Query Failed
A high-concurrency JDBC query failed.
Slow JDBC Query
A high-concurrency JDBC query takes too long to execute.
- Browse to the SpringSource tc Runtime 7.0 Tomcat JDBC Connection Pool Global service associated with your JDBC data source.
- Click the Inventory tab.
- In the Configuration Properties section, verify that the
service.log_track.enableproperty is selected.
Selecting this property subscribes vRealize Hyperic to JMX notifications sent from the tc Runtime instance, which are then displayed in vRealize Hyperic as log events.