Instrument the DefaultDomain for Standalone Applications

By default, the .NET Agent does not instrument the .NET DefaultDomain AppDomain. Before you instrument the DefaultDomain:

• Follow the instructions to instrument a standalone application
• Create a POCO entry point for a class/method in the application

If you complete those steps and still do not see business transactions in the Controller, check if your managed code runs in the DefaultDomain. If so, you must configure the agent to instrument the DefaultDomain.

Check if Your Application Runs in the DefaultDomain

If you are unfamiliar with your application's managed code, you can use the agent logs to identify the AppDomain.

1. Open the agent log:
   Windows Server 2008 and later: %ProgramData%\AppDynamics\DotNetAgent\Logs\AgentLog.txt
2. Search the agent log for AppDomain.
   

   Few log entries contain AppDomain when the agent starts up. Look for an entry by dllhost or your instrumented application similar to the following:

   2013-12-16 08:23:02.3120 3068 MYPROGRAM 1 1 Info Configuration appDomainName=DefaultDomain appDomainId=1 iis-app=null site=null port=null appPoolId=
   2013-12-16 08:23:02.6240 3192 dllhost 1 17 Info ConfigurationManager Not instrumenting DefaultDomain for pid 3068
   

   CODE

   In this example, MYPROGRAM is the name of the instrumented standalone application. You can see the name of the AppDomain in the log entry, appDomainName=DefaultDomain.

Instrument the DefaultDomain

1. Open the config.xml file for editing as administrator.  See 'Where to Configure Agent Properties' on Administer the .NET Agent

2. Copy the code block below to a child element of the standalone-application element. See .NET Agent Configuration Properties

       <profiler>
           <instrument-defaultdomain enabled="true"/>
       </profiler>

   CODE

    The Profiler element must follow the Standalone Application Tier element.

   For example:

   <?xml version="1.0" encoding="utf-8"?>
   <appdynamics-agent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
     <controller host="mycontroller.mycompany.com" port="8090" ssl="false">
       <application name="My Business Application" />
   	<account name="customer1" password="changeme" />
     </controller>
     <machine-agent />
     <app-agents>
       <IIS>
           <applications />
       </IIS>
       <standalone-applications>
         <standalone-application executable="MyStandaloneApp.exe">
           <tier name="Standalone Tier" />
           <profiler>
               <instrument-defaultdomain enabled="true"/>
           </profiler>
         </standalone-application>
       </standalone-applications>
     </app-agents>
   </appdynamics-agent>

   CODE
3. Save the config.xml file.
4. Restart the AppDynamics.Agent.Coordinator service.
5. Restart the standalone application for your changes to take effect.