Splunk AppDynamics

How to Manage Call Graphs

CommunityUser
Splunk Employee
Splunk Employee

Hi,

We're facing issue with Transaction response time in call graph .

We're facing Partial call graphs in more numbers in the list compare to full graph details. So whenever APP team reports slowness issue , we're unable to get the execution time of a BT call in full range from end to end.

Partial graphs show some exec time in view list and show diff execution time while i drill down.

For Ex in list view it shows me 19,282ms, When i drill down it shows only 435ms.

Could some one please help how can i effectively manage call graphs, as i'm facing issue due to this.

Because APP team raising concern reg this and we need to get FULL call graphs for this particular application for troubleshooting reasons.


Regards,

Soundarajan

Labels (1)
0 Karma

CommunityUser
Splunk Employee
Splunk Employee

The example that you provided is of a transaction snapshot for a slow transaction in which AppD was not intially collecting a snapshot but then detected the transaction as slow and hence collected the snapshot for the remaining flow.

You can configure the transaction snapshot settings as well, details on the links below:

https://docs.appdynamics.com/display/PRO44/Transaction+Snapshots

https://docs.appdynamics.com/display/PRO44/Transaction+Snapshot+Collection

For call graph settings, refer to: https://docs.appdynamics.com/display/PRO44/Call+Graph+Settings

0 Karma
Get Updates on the Splunk Community!

Observability Unlocked: Kubernetes Monitoring with Splunk Observability Cloud

  Ready to master Kubernetes and cloud monitoring like the pros?Join Splunk’s Growth Engineering team for an ...

Wrapping Up Cybersecurity Awareness Month

October might be wrapping up, but for Splunk Education, cybersecurity awareness never goes out of season. ...

🌟 From Audit Chaos to Clarity: Welcoming Audit Trail v2

🗣 You Spoke, We Listened  Audit Trail v2 wasn’t written in isolation—it was shaped by your voices.  In ...