Splunk AppDynamics

Servlet transaction's call graph is not shown

CommunityUser
Splunk Employee
Splunk Employee

I manually triggered a diagnostic session to capture some snapshots of a servlet service deployed on WSO2 DSS. Snapshots are taken, but I'm not able to see the complete call graph, seeing only the first line. Execution time was 18 ms. See the below screenshot. What should I do to see the call graph?

image.png

Labels (1)
0 Karma

CommunityUser
Splunk Employee
Splunk Employee

I was able to get the call graph when the execution time is bit high, around 400ms. See the below screenshot. Question is, what should be the minium execution time inorder for appdynamics to be able to capture the call graph? I read somewhere it's only 10 ms, but it doesn't seem to be the case.

image.png

0 Karma

Peter_Holditch
Builder

Business Transaction execution within a snapshot is profiled every 10ms, as you state.  In your 18ms snapshot, it is likely that whatever methods within the servlet ran did not individually last long enough to be detected by the profiler.

Given the short execution time I would imagine that whatever these methods are, they are unlikely to represent a performance problem.

Warm regards,

Peter

0 Karma
Get Updates on the Splunk Community!

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...

Splunk Observability for AI

Don’t miss out on an exciting Tech Talk on Splunk Observability for AI!Discover how Splunk’s agentic AI ...

🔐 Trust at Every Hop: How mTLS in Splunk Enterprise 10.0 Makes Security Simpler

From Idea to Implementation: Why Splunk Built mTLS into Splunk Enterprise 10.0  mTLS wasn’t just a checkbox ...