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
03-31-2024 11:38 PM
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.
For the similar application where JDBC details are not captured.
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
Solved! Go to Solution.
04-10-2024 04:41 AM
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...
Thank you! Your submission has been received!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form