You can configure the .NET Agent to monitor ASP.NET applications with multiple Application Domains (AppDomains). This page assumes that you have a working knowledge of AppDomains and are familiar with the AppDomain implementation in your application.
This page does not describe the System Domain, Shared Domain, or DefaultDomain AppDomains that the CLR instantiates before it executes the managed code. If your standalone application runs in the DefaultDomain, see Instrument the DefaultDomain for Standalone Applications.
AppDomains in .NET
Windows uses processes to manage security and performance isolation between running applications. Process isolation ensures that the application's running code does not interfere with another application. However for applications that share data, making calls between Windows processes can introduce complications and performance issues. AppDomains enable developers to create several applications that run inside a single process but maintain application isolation.
Single Application Domain
When a single application runs inside its own process, the runtime host manages the AppDomain. The application executable and the AppDomain have the same name. The .NET Agent installs itself inside the single AppDomain and creates a node for the application.
Multiple Application Domains
When developers include multiple AppDomains in an application, all the AppDomains run inside a single process. The application executable may have the same name as one AppDomain, but there are other, uniquely-named AppDomains. By default, the agent installs itself inside all the AppDomains and creates nodes for them.
Configure Monitoring for Multiple Application Domains
If the application you monitor contains multiple AppDomains, the App Agent for .NET automatically instruments each AppDomain and creates a node. You can configure the .NET Agent to instrument only the AppDomains you specify. Use this to exclude AppDomains you do not want to monitor, and to limit the number of nodes in a tier.
You can configure application domain monitoring for:
- Windows Services
- Standalone Applications
Configure all instrumentation settings for the .NET Agent in the config.xml file. See Administer the .NET Agent.
Identify the name of the AppDomains to instrument.
If you have already instrumented your application, the AppDomain names display in the Node Dashboard.
Click the node in the left navigation pane, then click CLR.
- Launch a text editor as administrator.
- Edit the
config.xmlfile as an administrator. See Administer the .NET Agent.
- Find the element that corresponds to your application with multiple AppDomains:
Standalone Application element:
app-domain-nameattribute to the element.
For example, to instrument the
MyApp.exe AppDomainfor the
<standalone-application executable="MyApp.exe" app-domain-name="MyApp.exe"> <tier name="StandaloneApplication Tier"/> </standalone-application>CODE
As soon as you instrument one AppDomain in the
config.xmlfile, the agent instruments only the AppDomains you specify. Other AppDomains are not instrumented.
To instrument additional AppDomains, add an element for each AppDomain as if they were separate applications.
For example, to instrument
<standalone-application executable="MyApp.exe" app-domain-name="MyAppDomain1"> <tier name="StandaloneApplication Tier"/> </standalone-application>CODE
- Save the
- Restart the
- Restart instrumented applications: Windows services or standalone applications.
Sample Standalone Application Configuration with Multiple AppDomains
config.xml file shows the configuration for the application,
MyApp.exe. Instrumentation only applies to the AppDomains specified in the
<?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"> <account name="customer1" password="changeme" /> <application name="MyDotNetApplication" /> </controller> <machine-agent /> <app-agents> <standalone-applications> <standalone-application executable="MyApp.exe" app-domain-name="MyApp.exe"> <tier name="StandaloneApplication Tier"/> </standalone-application> <standalone-application executable="MyApp.exe" app-domain-name="MyAppDomain2"> <tier name="StandaloneApplication Tier"/> </standalone-application> </standalone-applications> </app-agents> </appdynamics-agent>