Related pages:

This page describes the .NET configuration properties you can set using Windows System Environment Variables. 

Agent Account Name

Specifies the account name for the SaaS or multi-tenant Controller.

Environment Variable: APPDYNAMICS.AGENT.ACCOUNTNAME
Type: String
Default: For single-tenant Controllers, the agent assumes the default of "customer1" if you do not specify an account name.
Required: Only for SaaS or multi-tenant Controllers.

Agent Application Name

Specifies the business application you use in the Controller. If the application name does not exist, the Controller will create it when the agent registers. See Overview of Application Monitoring.

Environment Variable: APPDYNAMICS.AGENT.APPLICATIONNAME
Type: String
Default: None
Required: Yes

Agent Account Password  

Specifies the account access key for the Controller. 

Environment Variable: APPDYNAMICS.AGENT.ACCOUNTACCESSKEY
Type: String
Default: None
Required: Yes

Agent Node Name

The name of the node.

In general, the node name must be unique within the business application and physical host. If you want to use the same node name for multiple nodes on the same physical machine, create multiple virtual hosts using the Unique Host ID property. See Unique Host ID.

Environment Variable: APPDYNAMICS_AGENT_NODE_NAME
Type: String
Default: None
Required: Yes

Agent Reuse Node Name

Set this environment variable to true to reuse node names in AppDynamics. When you set the property to true, you don't need to supply a node name, but you do need to provide a node name prefix using appdynamics.agent.reuse.nodeName.prefix.

This property is useful for monitoring environments where there are many CLRs with short life spans. When true, AppDynamics reuses the node names of historical CLRs for new CLRs. This avoids a proliferation of differently named nodes in AppDynamics over time, particularly when the nodes are essentially identical processes that run over different times. 

AppDynamics generates a node name with App, Tier, and Sequence number. The node names are pooled. For example, the sequence numbers are reused when the nodes are purged (based on the node lifetime).

When the .NET Agent starts up, it logs output to the console until it registers with the Controller and the Controller generates the node name. 

The Controller reuses node names based on the node.retention.period property.

Environment Variable:  appdynamics.agent.reuse.nodeName
Type: Boolean
Default: False
Required: No

Example: Using the following environmental variable specifications, the Controller generates a node name with the prefix "reportGen". Node names will have suffixes --1, --2, and so on, depending on the number of nodes are running in parallel. The name of a node that is shut down and qualifies as a historical node may be reused by a new node. 

appdynamics.agent.reuse.nodeName=true

appdynamics.agent.reuse.nodeName.prefix=reportGen

Agent Reuse Node Name Prefix

When you configure the agent to reuse node names, use this property to specify the prefix the Controller uses to generate node names dynamically.  

Environment Variable: appdynamics.agent.reuse.nodeName.prefix
Type: String
Default: None
Required: When  appdynamics.agent.reuse.nodeName=true
Example: Using the following environmental variable specifications, the agent directs the Controller to generate a node name with the prefix "reportGen". Node names will have suffixes --1, --2, and so on, depending on how many nodes are running in parallel.

appdynamics.agent.reuse.nodeName=true

appdynamics.agent.reuse.nodeName.prefix=reportGen

Agent Tier Name

Specifies the name of the tier that this .NET node belongs to. Note that this is not the deployment name on the application server.

Environment Variable: APPDYNAMICS_AGENT_TIER_NAME
Type: String
Default: None

Required: Yes

Agent Unique Host ID

Logically partitions a single physical host or virtual machine such that it appears to the Controller that the application is running on different machines. Set the value to a string that is unique across the entire managed infrastructure. The string may not contain any spaces. If you have a machine agent associated with the application monitored by the app agent, then this property must be set on the machine agent to the same value. See Standalone Machine Agent Installation Scenarios.

Environment Variable: APPDYNAMICS_AGENT_UNIQUE_HOST_ID
Type: String
Default: None
Required: No

AWS Instance ID

If the app that you are instrumenting runs on AWS, then .NET Agent supports collecting the AWS Instance ID. To collect the AWS Instance ID, set APPDYNAMICS.AWS.INSTANCE.ENABLED=true

Environment Variable: APPDYNAMICS.AWS.INSTANCE.ENABLED
Type: Boolean
Default: false
Required: No

Controller Hostname

Specifies the hostname or the IP address of the AppDynamics Controller. For an on-premises Controller, use the value for Application Server Host Name you provided when you installed the Controller. If you use the AppDynamics SaaS Controller, see the Welcome email from AppDynamics for the name of your Controller. 

Environment Variable: APPDYNAMICS.CONTROLLER.HOSTNAME
Type: String
Default: None
Required: Yes, may also be set in the agent config.xml file or using the agent configuration utility.

Controller Port Number

Specifies the HTTP(S) port of the AppDynamics Controller. If the APPDYNAMICS.CONTROLLER.SSL.ENABLED environment variable is set to true, specify the HTTPS port of the Controller; otherwise, specify the HTTP port. 

Environment Variable: APPDYNAMICS.CONTROLLER.PORT
Type: Positive Integer
Default: 8090

  • For On-premises installations, the defaults are port 8090 for HTTP and port 8181 for HTTPS.
  • For the SaaS Controller, use port 80 for HTTP or port 443 for HTTPS.

Required: Yes, may also be set in the agent config.xml file or using the agent configuration utility.

Controller SSL Enabled 

When set to "true" enables encryption over SSL between the agent and the Controller.

Environment Variable: APPDYNAMICS.CONTROLLER.SSL.ENABLED
Type: Boolean
Default: false

Required: No, may also be set in the agent config.xml file or using the agent configuration utility.

Reference of Environment Variables

The .NET Agent (through the config.xml file) can reference any environment variables when configuring Agent Node Name, Agent Tier Name, or Controller Application Name.

These environment variables can be referenced in the configuration file or in the agent environment variables for the node, tier, and application names listed above. 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.