AppD Archive

How to profile a thread in a .NET request ?

CommunityUser
Splunk Employee
Splunk Employee

Hi,

My .NET web applicaion spawns three threads inside it. 

But in the appdynamics call graph i can see only the functions in the main thread of the request. But i cannot see the function calls that belongs to the three threads of that request.

Should i set any configuration setting to profile the threads in the request ?

Regards,

./Rahul

Tags (4)
0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Can i get any reply regarding this thread ?

Venu_Babu_Thang
Communicator

Hi,

Please follow the below steps to see the thread correlation between the threads.

  1. Add the below section in the Config.xml file and save the file.
    <machine-agent>
        <instrumentation>
            <instrumentor name="ThreadCorrelationThreadPoolCLR2Instrumentor" enabled="true"/>
            <instrumentor name="ThreadStartCLR2Instrumentor" enabled="true"/>
            <instrumentor name="ThreadStartCLR4Instrumentor" enabled="true"/>
        </instrumentation>
      </machine-agent>
  2. Then add the following property "thread-correlation" in the Controller UI for the web applicaion tier.
  3. Then restart the AppDynamics Agent Coordinator service and the IIS.
  4. Then generate the traffic on the application for 5-10 mins and then check the snapshots to see if all the threads are showing.

Please let us know if you still face any issues.

Thanks,

Venu.

0 Karma
Get Updates on the Splunk Community!

September Community Champions: A Shoutout to Our Contributors!

As we close the books on another fantastic month, we want to take a moment to celebrate the people who are the ...

Splunk Decoded: Service Maps vs Service Analyzer Tree View vs Flow Maps

It’s Monday morning, and your phone is buzzing with alert escalations – your customer-facing portal is running ...

What’s New in Splunk Observability – September 2025

What's NewWe are excited to announce the latest enhancements to Splunk Observability, designed to help ITOps ...