Not a customer? Click the 'Start a free trial' link to begin a 30-day SaaS trial of our product and to join our community.
Existing Cisco AppDynamics customers should click the 'Sign In' button to authenticate to access the community
08-08-2023 08:07 PM
Hello,
I am facing issue, in my Java agent application i couldn't find JDBC connection pool details there is only thread details available, anyone have any idea about this and how to resolve this issue?
08-09-2023 03:58 PM
Hello @Shubham.Wagdarkar,
I found this existing info. I'm not sure what Controller version you are on, so you may need to adjust the documentation to fit the right version #.
Please search the MBean Browser and see if you can find the metric:
https://docs.appdynamics.com/21.12/en/application-monitoring/configure-instrumentation/configure-jmx...
If it is not visible in MBean Browser, then it means that the metric has not been exposed on the Spring Boot side. Can you see the metric in JConsole?
https://docs.oracle.com/javase/7/docs/technotes/guides/management/jconsole.html
If you need another way besides Mbeam to get JDBC Connection pool metrics, you can try this.
For some frameworks, for example if you are using Tomcat, then the connection pools should be found by the default detection rules under DataSource if you are using org.apache.tomcat.jdbc.pool.DataSource and set the flag jmxEnabled=true:
https://tomcat.apache.org/tomcat-8.5-doc/jdbc-pool.html
However, if you are not already seeing the metric then it is not at one of the locations where we would auto-detect it, and it would be necessary to find the metric in MBean Browser.
Thanks,
Ryan, Cisco AppDynamics Community Manager
Found something helpful? Click the Accept as Solution button to help others find answers faster.
Liked something? Click the Thumbs Up button.
Check out Observabiity in Action
new deep dive videos weekly in the Knowledge Base.
User | Count |
---|---|
2 | |
1 | |
1 | |
1 | |
1 |
Thank you! Your submission has been received!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form