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 depend on the metric data collection extension and the machine's OS. See Machine Agent Metric Collection.
The Azul JRE is included as a component in the AppDynamics products and modules. In response to how often Oracle produces and distributes JRE/JDK 8, AppDynamics replaced Oracle JRE with Azul JRE in the 20.5.0 Machine Agent.
The Machine Agent requires a Java Virtual Machine (JVM). Downloads for many of the supported operating systems include Azul JRE 1.8.0_262. The Machine Agent should work with most of the JVMs supported by the Java Agent JRE 1.8. However, it is extensively tested only for the Azul JRE.
- For tested platforms listed in the table, AppDynamics recommends using the latest available Machine Agent release from the AppDynamics Downloads page.
- For Linux Flavors, the Machine Agent is bundled with Azul JRE 11. For Windows and Solaris, the Machine Agent is bundled with Azul JRE 1.8
If you upgrade the Linux Machine Agent to 21.1.0, then you must also upgrade all extensions to their latest versions to support Machine Agent 21.1.0.
- To run the Machine Agent on other platforms (such as AIX or HP-UX), use the unbundled Machine Agent ZIP without the JRE. For these platforms, you must install JRE 1.8 on the Machine Agent host.
- 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. To handle large values for metrics, run the Machine Agent using a 64-bit JDK.
Linux and Solaris agents require Bash >=3.1.
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 |
|Architecture x64 (64-bit)||Architecture SPARC (64-bit)|
Linux / CentOS
Linux / Debian
|Linux / Fedora||Yes||No|
|Linux / openSUSE Leap||Yes||No||42.3, 15.0|
|Linux / Red Hat Enterprise Linux||Yes||No|
6, 7, 8
|Linux / SUSE Linux Enterprise||Yes||No||12, 15|
Linux / Ubuntu
14.04, 16.04, 18.04
2012 R2, 2016, 2019
These other platforms (supported by JRE 1.8), should also be compatible with the Machine Agent. However, AppDynamics has not fully tested them.
- 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: One 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. 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 set this flag through the
JAVA_OPTS environment variable on your system. For example, if you enter:
export JAVA_OPTS="-Xms20m -Xmx128m" on Linux, this sets 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 require more heap space; the amount required depends on how you code the extension. If you start adding extensions, you should 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