https://community.splunk.com/t5/Splunk-AppDynamics/To-Track-particular-Thread-and-Session/m-p/739378#M11392 <P>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.</P><P>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.</P> Wed, 18 Sep 2019 18:02:04 GMT millerep 2019-09-18T18:02:04Z https://community.splunk.com/t5/Splunk-AppDynamics/To-Track-particular-Thread-and-Session/m-p/739377#M11391 <P>There is a load test in the test environment. During the test, I noticed certain business transactions took a lot of time.</P> <P>For ex: In a 1-hour load test, there will be nearly 15K transactions and 10 transactions took more time.</P> <P>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.</P> <P>How do I track the flow using these details in AppDynamics?</P> <P>Kindly help.</P> Wed, 18 Sep 2019 16:59:39 GMT https://community.splunk.com/t5/Splunk-AppDynamics/To-Track-particular-Thread-and-Session/m-p/739377#M11391 CommunityUser 2019-09-18T16:59:39Z https://community.splunk.com/t5/Splunk-AppDynamics/To-Track-particular-Thread-and-Session/m-p/739378#M11392 <P>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.</P><P>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.</P> Wed, 18 Sep 2019 18:02:04 GMT https://community.splunk.com/t5/Splunk-AppDynamics/To-Track-particular-Thread-and-Session/m-p/739378#M11392 millerep 2019-09-18T18:02:04Z