On this page:

Related pages:

Highly-scaled environments frequently contain multiple machines that run the same .NET applications and therefore use the same AppDynamics .NET Agent configuration. Manual configuration updates to several machines can be tedious and error-prone.

Use the Config Management tool in the AppDynamics Controller to upload and manage .NET Agent config.xml files. By default the .NET Agent checks for configuration updates from the controller every minute. Use the Config Management tool assign configurations to machines where the .NET Agent is running.

Click Settings > AppDynamics Agents > Config Management to manage all the .NET Agent configurations files for your machines.


.NET agents deployed on Azure cloud services using the AppDynamics NuGet package do not register for Config Management because web role and worker role machine names are not always unique. Duplicate machine names could lead to unexpected consequences. 

Identify Configuration File

To start managing your configurations in the Controller, identify a configuration file or set of configuration files to upload. If you're not familiar with .NET Agent configuration, AppDynamics recommends you use the Agent Configuration Utility on each machine to configure the agent. For more information, see Administer the .NET Agent and Configure the .NET Agent.

For a full list of configuration properties, see .NET Agent Configuration Properties.

Import Configuration

The Import Config dialog lets you upload a config.xml file to the Controller and specify a unique name for the configuration.

Assign Configuration to Machines

The Config Management tool lets you assign machines to a configuration or change the configuration from one to another. After you assign the configuration in the Controller the .NET Agent automatically downloads the configuration file.

Opt Out of Config Management

To configure an agent so that it does not receive configuration files from the Controller, set the Controller enable config deployment attribute to false in the config xml. See "Controller Element' on .NET Agent Configuration Properties. For example:

<controller host="mycontroller.saas.appdynamics.com" port="443" ssl="true" enable_config_deployment="false"> 

Restore an Old Configuration

If you mistakenly assign a configuration, use the following steps to restore a previous version of the config.xml:

  1. On the Config Management window, drag the machine from its currently assigned config to Machine with no assigned templates.
  2. On the machine itself, rename the existing configuration file, config.xml, to a name such as config.old.xml.
  3. Copy the backup config file from the Backup subdirectory to the Config directory. Backup files are named in the following format: config-<date>.xml. 
  4. Rename the backup config file to config.xml.
  5. Optionally edit the config.xml to opt out of Config Management.
  6. Restart the AppDynamics Agent Coordinator service.
  7. Restart Windows services, instrumented Windows services, and instrumented standalone applications.