Independent Machine Agent Install Scenario
Typically, you only use the following properties if you are installing the Machine Agent on a server that does not have any AppDynamics App Agents installed.
Application Name
The name of the logical business application that this JVM node belongs to. This is not the deployment name (ear/war/jar) on the application server. If a business application of the configured name does not exist, it is created automatically.
Element in controller-info.xml: <application-name>
System Property:- Dappdynamics.agent.applicationName
Environment Variable: APPDYNAMICS_AGENT_APPLICATION_NAME
Type: String
Defaults: None
Required: No. See Machine Agent Installation Scenarios.
Node Name
The name of the JVM node. When not specified, this defaults to Node1 for the Machine Agent.
Element in controller-info.xml: <node-name>
System Property:- Dappdynamics.agent.nodeName
Environment Variable: APPDYNAMICS_AGENT_NODE_NAME
Type: String
Defaults: None
Required: No. See Machine Agent Installation Scenarios.
Tier Name
The name of the logical tier that this JVM node belongs to. This is not the deployment name (ear/war/jar) on the application server. If a tier of the configured name does not exist, it is created automatically.
Element in controller-info.xml: <tier-name>
System Property:- Dappdynamics.agent.tierName
Environment Variable: APPDYNAMICS_AGENT_TIER_NAME
Type: String
Defaults: None
Required: No. See Machine Agent Installation Scenarios.
Exclude File Cache Memory from Memory Usage
You can use the following system property to exclude the file cache memory while calculating memory usage on AIX with server visibility enabled.
-Dappdynamics.machine.agent.collect.memoryMetrics.using.vmstat.command = true> and <sim_enabled = true> for AIX, you get memory usage metrics on the Controller UI after excluding the file cache memory.System Property: -
Dappdynamics.machine.agent.collect.memoryMetrics.using.vmstat.command
Environment Variable: N/A
Type: Boolean
Default: false
Required: No