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
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Where Innovation Takes Flight: The Splunk4Aviation Flight Sim Lands at .conf26

If you hear someone at .conf26 shouting "gear down, GEAR DOWN" across the show floor, you have found us.  The ...

Turn Cisco Telemetry Into Action with Cisco Data Fabric, powered by the Splunk ...

The surge in machine data is already hitting enterprise budgets, and the agentic era will only intensify it. ...

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...