By default, the .NET Agent does not instrument the .NET
DefaultDomain AppDomain. Before you instrument the
- 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
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.
- Open the agent log:
Windows Server 2008 and later:
- Search the agent log for
Few log entries contain
AppDomain'when the agent starts up. Look for an entry by
dllhostor your instrumented application similar to the following:
In this example,
MYPROGRAMis the name of the instrumented standalone application. You can see the name of the AppDomain in the log entry,
Instrument the DefaultDomain
config.xmlfile for editing as administrator. See 'Where to Configure Agent Properties' on Administer the .NET Agent
Copy the code block below to a child element of the
standalone-applicationelement. See .NET Agent Configuration Properties
The Profiler element must follow the Standalone Application Tier element.
- Save the
- Restart the
- Restart the standalone application for your changes to take effect.