cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

java_agent not discovering the JDBC calls

Akshay.Nimbal
Builder

Hi,

We are running many applications with JAVA_AGENT and out of those, a few applications are discovering the JDBC calls and a few are not discovering the JDBC backend. I even tried to manually add a custom discovery with rule of matching URL. What all other factors impacting this and anything needs to be changed? Have attached the samples here.

Note:

1. Both apps are using same version of MySQL connector jar.  mysql-connector-java : 5.1.49

For the application where the JDBC details and queries are captured. 

AkshayNimbal_0-1711953278668.png

For the similar application where JDBC details are not captured.

AkshayNimbal_1-1711953399855.png

Note: 

1. For the app where details are captured is a web-app where business-transaction are present. but for the app where this is not captured is a core java app without transaction. ( More like a monitoring app ). Does this have any impact?

 

Thanks & Regards.

Akshay

 

1 REPLY 1

Akshay.Nimbal
Builder

After discussing with AppDynamics support, we found these observations and solution.

The reason you are not observing any database calls is that not a single Business Transaction has been detected. The agent only detects outgoing calls if they occur within the context of a Business Transaction (BT).
 
Next steps
Please apply the below-mentioned node property:

Name: find-entry-points
Type: Boolean
Value: True

This property will enable a feature that will recognize all the potential entry points that can be created as custom match rules.

For more information on how to set/change node property please check the reference doc:


Once you will change the property value, collect the Agent debug log files and share them with us. Then revert the change.

Reference doc:

We found a couple of potential entry points that will allow you to monitor JDBC calls by enabling the 
 
Next steps
Please create BT POJO on the following class/method:
 
BT-1

Class: com.imi.timer.quartz.cronjobs.PauseCampaignMonitor
Method: execute

 
BT-2

Class: com.imi.timer.quartz.cronjobs.StopCampaignMonitor
Method: execute

 
BT-3

Class: com.imi.timer.quartz.cronjobs.AbandonedTargetsMonitor
Method: execute

 
BT-4

Class: com.imi.imicampaign.security.cache.CustomerDetailsCacheManager
Method: updateCustomerKeyDetailsCache

 
BT-5

Class: com.imi.timer.quartz.cronjobs.InstanceDetailsUpdateMonitor
Method: execute

 
#Doc POJO BT
https://docs.appdynamics.com/appd/24.x/24.3/en/application-monitoring/configure-instrumentation/tran...
 

June 26 Webinar
Discover new Splunk integrations and AI innovations for Cisco AppDynamics.


Register Now!

Observe and Explore
Dive into our Community Blog for the Latest Insights and Updates!


Read the blog here