This page lists the application environments and versions supported by the Machine Agent. Any environments or versions that are not listed are not supported.
Machine Agent Supported Platforms
Supported platforms and environments for the Machine Agent are dependent on which metric data collection extension is being used. This depends on the machine's OS. See Machine Agent Metric Collection.
AppDynamics is replacing Oracle JRE with Azul JRE, as a component included in the AppDynamics products and modules, and distributed to its customers. This change occurred in the 20.5.0 Machine Agent.
The Machine Agent requires a Java Virtual Machine. In response to the number of changes in how Oracle's JRE/JDK 8 is produced and distributed, AppDynamics is replacing Oracle JRE with Azul JRE, as a component included in the AppDynamics Machine Agent. Downloads for many of the supported OSs include Azul JRE 8.0.252. The Machine Agent should work with most of the JVMs supported by the Java Agent that are JRE 1.8. However, it is extensively tested only for the Azul JRE.
For the available Machine Agent downloads:
- For tested platforms listed in the following table, AppDynamics recommends using the bundled version of the 4.4 Machine Agent.
- To run the Machine Agent on other platforms (such as AIX or HP-UX), use the unbundled Machine Agent ZIP without the JRE. The agent host must have JRE 1.8 installed.
- If you are using a 64-bit Operating System, use only a 64-bit JRE.
A 64-bit long has a maximum and minimum value of 9223372036854775807 and -9223372036854775808, respectively, whereas a 32-bit long has a maximum and minimum value of 2147483647 and -2147483648, respectively. To handle large values for metrics, run the Machine Agent using a 64-bit JDK.
Bash RequirementsLinux and Solaris agents require Bash 3.1 or higher.
Linux systems must include the
This table provides instructions on how to install the library on some common flavors of Linux operating systems.
|Red Hat and CentOS|
|Fedora||Install the library |
|Debian||Use a package manager such as |
|x86 (32-bit)||x64 (64-bit)||SPARC (64-bit)|
Linux / CentOS
Linux / Debian
|Linux / Fedora||Yes|
|Linux / openSUSE Leap||Yes||42.3|
|Linux / Red Hat Enterprise Linux|
|Linux / SUSE Linux Enterprise||Yes||12|
Linux / Ubuntu
Windows Server 2012 R2
|Yes||Windows Server 2016|
Other operating systems and versions that are supported by JRE 1.8 should also work but are not fully tested by AppDynamics.
- Oracle JRE 1.8
- IBM SDK, Java Technology Edition, Version 8
- HP JDK/JRE 8
You should be able to run the Bundled version of the Machine Agent on machines based on Power Architecture processors, including PowerPC processors, but Server Visibility is not supported on these platforms.
Hardware and Sizing Requirements
Agent: 1 additional GB of RAM.
Controller: Although we recommend that you install the AppDynamics Controller on a dedicated server, in some cases the Machine Agent can co-exist with the Controller on the same system. A Controller with more than 250 nodes must run on a dedicated machine. The exact number of Machine Agents that can be supported depends on whether other agents are reporting to the same controller and whether the Machine Agents have Server Visibility enabled (more metrics are generated under Server Visibility). See Controller System Requirements
JVM Memory Requirements
The lightweight Machine Agent consumes minimal resources of your computer.
AppDynamics recommends the following additional Heap and PermGen space to accommodate the agent:
Maximum heap size (-Xmx): 256 MB
Maximum PermGen heap size (-XX:MaxPermSize): 20 MB
By default, the JVM maximum heap size is set to 256 MB. To override this setting, you can specify this flag through the
JAVA_OPTS environment variable on your system. For example, on Linux if you enter:
export JAVA_OPTS="-Xms20m -Xmx128m"
This will set the initial heap size to 20 MB and the max heap size to 128 MB.
The exact CPU or memory overhead added by the agent can vary based on the extensions used and whether the extensions are Java. Java extensions need more heap space; the amount required depends on how the extension is coded. If you start adding extensions, increase the maximum heap space to 256 MB or 512 MB. Additionally, you may need to increase the size of the initial memory allocation. Monitor the memory consumption of the agent to ensure that there are sufficient resources allocated to it. You can also enable Garbage Collection logging on the JVM to help tune the heap size for the extensions.
Example settings for increasing the initial heap size:
Linux and Unix systems:
cscript <machine_agent_home>\machine-agent.vbs -Xms64m