Splunk AppDynamics

To Track particular Thread and Session

CommunityUser
Splunk Employee
Splunk Employee

There is a load test in the test environment. During the test, I noticed certain business transactions took a lot of time.

For ex: In a 1-hour load test, there will be nearly 15K transactions and 10 transactions took more time.

I need to analyze the flow of the problematic transactions. For ex: I have the Thread id and Session id of one of the particular transactions.

How do I track the flow using these details in AppDynamics?

Kindly help.

Labels (1)
0 Karma

millerep
Contributor

If you have a baseline set and these slow transactions are beyond that threshold, then you should be able to see a call graph of the offending transactions. To do this, click on the "Applications" tab, and then click on the application with the slow response times. From there, on the left-hand side you can either expand out "Troubleshoot" and then click on errors and look for Transaction Snapshots with a "blue page icon", and double-click on it, and then drill down from there, or you can click on "Business Transacations", double-click on the transaction with the long times, and then click on "Slow transactions" or "Transaction Snapshots" and double-click on snapshots with the "blue page icon." If you go this last route, you should be able to double-click on a healthy one and a bad one to compare your call charts.

In the future, you can set a Policy to trigger when it goes beyond your baseline too, and get a direct deeplink to the offending transactions.

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!

Mastering Threat Intelligence in ES 8.5, Splunk AI Assistant v2, and More from Splunk ...

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...

Break the Build: Inside the KubeDoom Lounge at .conf26

    You step up to the machine. The pixelated corridors of a certain 1993 FPS load in front of you, EMP Pulse ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...