PDFs


This page applies to an earlier version of the AppDynamics App IQ Platform.
See the latest version of the documentation.


Skip to end of metadata
Go to start of metadata

On this page:

This topic lists the application environments and versions supported by the Standalone Machine Agent. Environments or versions that are not listed are not supported. For general information about AppDynamics support, see Supported Environments and Versions.

 

Supported Platforms for the Standalone Machine Agent

Supported platforms and environments for the Standalone Machine Agent are dependent on the specific metric data collection extension being used, which is dependent on the machine's OS. See Machine Agent Metric Collection for details.

JRE Requirements

The Standalone Machine Agent requires a Java Virtual Machine. JRE 1.7 or higher is required. Downloads for many of the supported OSs include Oracle JRE 1.8. The Standalone Machine Agent should work with most, if not all, of the JVMs supported by the Java Agent that are JRE 1.7 or higher. However, it is extensively tested only for the Oracle JDK and OpenJDK.

Note the following about the available Machine Agent downloads:

  • A Machine Agent ZIP without the JRE is available for AIX, HP-UX, and other machines that support JRE 1.7.
  • The downloads that bundle the JRE only run on x86 machines. To run the Machine Agent on other machine architectures, use the Machine Agent ZIP without the JRE.
  • If you are using a 64-bit Operating System, use only a 64-bit Java Runtime Environment (JRE).

 

Note on handling large metric values. A 64-bit long has a maximum and minimum value of 9223372036854775807 and -9223372036854775808 respectively, where as 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. 

Supported Environments

Tested Platforms

OS

Architecture

Versions

Kernel Version

CentOS

x86 (32-bit)

x64 (64-bit)

5.11, 6.6

2.6 and higher

Debian

x86 (32-bit)

x64 (64-bit)

7

2.6 and higher

Fedora

x86 (32-bit)

x64 (64-bit)

2.1

2.6 and higher

OpenSuSE

x86 (32-bit)

x64 (64-bit)

12.3, 13.2

2.6 and higher

Ubuntu

x86 (32-bit)

x64 (64-bit)

12, 14

2.6 and higher

Windows

x86 32-bit

x64 (64-bit)

Windows Server 2008 SP2

Windows Server 2012 R2

Windows 8.x

N/A

Other Platforms

Other operating systems and versions that are supported by JRE 1.7 should also work, but are not fully tested by AppDynamics. 

The Standalone Machine Agent is not supported on machines based on Power Architecture processors, including PowerPC processors.

Hardware and Sizing Requirements

Agent: 1 additional GB of Ram

Controller: Although we recommend that the AppDynamics Controller be installed on a dedicated server, in some cases the Standalone 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 Monitoring enabled or not (more metrics are generated under Server Monitoring). For more information, see Controller System Requirements.

JVM Memory Requirements

The lightweight Standalone 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): 100 MB
  • Maximum PermGen heap size (-XX:MaxPermSize): 20 MB

 

Extension Considerations

The exact CPU or memory overhead added by the agent can vary depending on the extensions used and whether the extensions are Java or not. Java extensions will 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 256MB or 512MB) to be safe. You may need to increase the size of the initial memory allocation as well. 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 being used. There are many resources on the Internet with advice on tuning Java memory management.

Example settings for increasing the initial heap size:

Linux and Unix systems: <machine_agent_home>/bin/machine-agent -Xms64m

Windows:  cscript <machine_agent_home>\machine-agent.vbs -Xms64m