Beginning in February 2020, AppDynamics switched from Semantic Versioning to Calendar Versioning for some agents and the first deployments of SaaS Controllers. In March 2020, the entire product suite will use Calendar Versioning.

Skip to end of metadata
Go to start of metadata

You use the AppDynamicsConfig.json file to:

  • Configure the connection settings to your Controller after installing your .NET microservices agent.
  • Disable instrumentation for troubleshooting.
  • Assembly whitelisting.
  • Disable inject fields.
  • Include blacklists and whitelists.

You can use environment variables in the AppDynamicsConfig.json file for node, tier, and application names. To include an environment variable, reference it by specifying %<variable>%, which can be combined with the other characters; for example, Web-%COMPUTERNAME" will be translated to Web-HOST23.

The following example .json file is just a sample and should not be copied/pasted into your AppDynamicsConfig.json file.

    "controller": {
        "host": "<<host_name>>",
        "port": 8080,
        "ssl": false,
        "enable_tls12": false,
        "account": "customer1",
        "password": "password",
        "proxy" : {
            "host": "test-host",
            "port": 8080,
               "username": "test-username",
               "password": "test-password",
               "domain": ""
    "application": {
        "name": "Dotnet",
        "tier": "tier1",
        "node": "node2"
	"instrumentors": {
    	"customCorrelationConfig": "custom-correlation.xml",
		"enable": [
    	"disable": [
  "assemblyWhitelist": [
        "Or any other regex"
	"disableInjectFields": false
    "profiler": {
         "attachBlackList": [ "ProcessNameToBeBlackListed", "ProcessNameToBeBlackListed", ... ],
         "attachWhiteList": [ "ProcessNameToBeWhiteListed", "ProcessNameToBeWhiteListed", ... ]
	"analytics": {
		"host": "localhost",
		"port": 9090

In 4.4.3, disableInjectFields are supported in .NET framework applications only.
In 4.5, disableInjectFields are supported in .NET core applications as well.

attachBlackList excludes a process if it is on the profiler list.
attachWhiteList excludes all processes except those listed in the list. If it is empty, it will include all processes.
Both lists relate to whether the profiler is detached from the process when the process launches, assuming the environment variables for the AppDynamics profiler are set correctly.

See Configure Custom Correlation for .NET Applications

  • No labels