As an alternative to using system properties or controller-info.xml to configure the application, tier, and node name, or other agent settings, you can use environment variables. Environment variables give you an additional option for configuring the agent based on dynamically set values.
About Environment Variables
To configure the agent with environment variables, simply set the value of the environment variables listed below to the value you want to use in the agent.
For example, if you set the value of the APPDYNAMICS_AGENT_NODE_NAME variable, as below, the agent automatically takes the value of node23 as its node name.
When settings are configured in different. Environment variable, system property and then controller-info.xml. The agent checks each for settings, and for a particular settings, uses the setting for the first of these (given the order of priority) that is not empty.
List of Variables
The following environment properties can be used today to configure the agent.
The following example would be resolved to a tierName=tier1 and a nodeName=node32
Related product doc links
For app and machine agent config properties
Q: What is the order of precedence of system properties, environment variables, and controller-info.xml.
Q: What happens if the settings conflict?
A: The order is followed and the first one that is non-empty is picked up.
Q: The above list covers many, but not all, of the system properties that are in the product docs. Is there one environment variable that corresponds to every property?
A: These are all the environment variables that we support.
Q: Are there additional environment variables to document that do not have corresponding properties?
Any Dev Followups?