The .NET Agent uses a single configuration file to control agent behavior and .NET Machine Agent behavior. The configuration file specifies Controller connectivity, .NET Machine Agent operations, and app agent functionality for IIS applications, Windows services, and standalone applications. The single configuration file lets you:
The AppDynamics Controller allows you to upload and manage .NET Agent configuration files. From the Controller, you can deploy a configuration to a machine or multiple machines where the agent is installed. See Manage Configuration for .NET.
Configure the agent properties in the config.xml file in the agent Config directory. To edit the config.xml, you must launch the editor as an administrator. When you run the .NET Agent Configuration Utility, it writes the conifg.xml to one of the following locations:
Windows Server 2008 and later
Windows Server 2003
For Windows Azure deployments, the .NET Agent NuGet pacakage contains the config.xml file. See Install the AppDynamics for Windows Azure NuGet Package.
Sample config.xml files install to the following location:
%ProgramFiles%\AppDynamics\AppDynamics .NET Agent\SampleConfigurations
After you edit the config.xml, you must restart the AppDynamics.Agent.Coordinator service. Then restart IIS, your Windows service, or standalone application for your instrumentation changes to take effect.
Some .NET Agent configurations require that you edit the config.xml:
Edit the config.xml file as an administrator.
Modify the xml according to the configuration instructions.
Save the config.xml.
The most basic configuration demonstrates the required sections for agent configuration. This sample instruments all IIS applications using the automatic element (
<automatic />). No Windows services or standalone applications are instrumented.
The configuration file that controls log files for the .NET Agent is located at:
The configuration file uses NLog configuration format.