Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: minor edits


  • Maintain agent configurations separately from web.config files.
  • Enable instrumentation of Windows services and standalone applications without environment variables.
  • Control agent behavior for specific applications with hierarchical configuration.

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 config.xml file to one of the following locations:


%ProgramFiles%\AppDynamics\AppDynamics .NET Agent\SampleConfigurations


After you edit the config.xml file, you must restart the AppDynamics.Agent.Coordinator service. Then restart your IIS services, your Windows service, services or standalone application applications for your instrumentation changes to take effect.



Appd net agent name
 configurations require that you edit the config.xml:

  1. Shut down the AppDynamics.Agent.Coordinator service.
  2. Edit the config.xml file as an administrator.

  3. Modify the XML file according to the configuration instructions.

  4. Save the config.xml file.

  5. Start the AppDynamics.Agent.Coordinator service.
  6. In some cases, you may need to restart IIS, instrumented Windows services, or instrumented Standalone applications. See individual
    Appd net agent name
     administration topics.


The most basic configuration demonstrates the required sections for agent configuration. This sample instruments all IIS applications using the automatic element (, <automatic />). AppDynamics does not instrument Windows services or standalone applications in this case.