Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.
AppDynamics customers and established members should click the sign in button to authenticate.
Please see the attached screen shot
We have been asked if AppDynamics excluding all class path libraries? If so, it won’t be possible to perform deep troubleshooting as most of the interesting stuff is missing, for example 30.2 sec call in PFS, but from call stacks we only see that the service was called and that’s it
Is there was way to instrumnet the app further or is this a limittaion in such scenarios? Please advise
How do we identify which package needs to be added? If you see the snapshot that i attached the drilldown just stops at 'Servlet:service' that has taken more than 30 secs. Does AppD expects to add package to drill down these common service calls that take longer time?
or could you please advise which package needs to be added in this specific case?
Appreciate you help!
Does not look like its stopping, i see another PJO call also recorded.
perhaps you need to talk to the App SME to deintify the flow and go from there.
or the other things you can do is, disable all the default excludes and see if you get more information on the call graph.
The question was initially raised by the AppDev, they doubt AppDynamics excluding all class path libraries to be drilled down to understand where exactly 30 secs is spent within "Servlet:service" as you see in the screenshot
What is trying to undertsnd is, this is a IBM webspehere App hat has been instrumented. Based on the callgraph that we see, what packages that need to be removed from exclusion list or even included. Could you suggest?
Also, doesnt look like we can exclude any packages list under "Call Graph Settings", except 'com.mongodb.connection.*' . If there are any specific sub-packages that can be included for IBM webspehere app, please let us know which ones and how.