PRO40 Server Monitoring 01july2015

Server Monitoring
AppDynamics Pro Documentation

Version 4.0.x
Page 1
Server Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Standalone Machine Agent Requirements and Supported Environments . . . . . . . . . . . . 3
Standalone Machine Agent Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Quick Install for the Standalone Machine Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Install the Standalone Machine Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Standalone Machine Agent Configuration Properties . . . . . . . . . . . . . . . . . . . . . . . . . 10
Install the Standalone Machine Agent as a Windows Service . . . . . . . . . . . . . . . . . . 16
Deploy Multiple Standalone Machine Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Configure Multiple Standalone Machine Agents for One Machine for Java . . . . . . . . 20
Resolve Installation Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Start the Standalone Machine Agent Automatically on Linux . . . . . . . . . . . . . . . . . . . 23
Start the Standalone Machine Agent Automatically on Windows . . . . . . . . . . . . . . . . 24
Associate Standalone Machine Agents with Applications . . . . . . . . . . . . . . . . . . . . . 25
Metrics Collected by the Standalone Machine Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Configure Metrics for Virtual Disks and External Network Traffic . . . . . . . . . . . . . . . . 27
Limit Disk Backup Metrics Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Configure Custom Metrics for the z-OS Machine Agent . . . . . . . . . . . . . . . . . . . . . . . 29
Extensions and Custom Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Build a Monitoring Extension Using Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Build a Monitoring Extension Using Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Standalone Machine Agent HTTP Listener . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
JVM Crash Guard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Remediation Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Administer the Standalone Machine Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Upgrade the Standalone Machine Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Determine Whether a Server is Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Controller Settings for Machine and Database Agents . . . . . . . . . . . . . . . . . . . . . . . . 57
Machine Agent FAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Page 2
Server Monitoring
Related pages:
Install the Standalone Machine Agent
Standalone Machine Agent Architecture
Metrics Collected by the Standalone Machine Agent
Machine Agent FAQ
Watch the video:
Standalone Machine Agent: An Overview
The Standalone Machine Agent is a standalone Java program that collects hardware-related
performance statistics from your servers. It can be deployed on any machine that hosts application
servers, database servers, messaging servers, Web servers, etc. It has an extensible architecture.
Use the Standalone Machine Agent to:
Collect basic metrics from the operating system that display in the Hardware tabs of
the Node Dashboard.
Report the metrics passed in by custom monitors.
Run remediation scripts for policy actions.
Run JVM Crash Guard.
Standalone Machine Agent Requirements and Supported

Environments
On this page:
Supported Platform Matrix for the Standalone Machine
Agent
Hardware Requirements
JVM Memory Requirements
CPU Consumption
Supported Platform Matrix for the Standalone Machine Agent
The Standalone Machine Agent provides platform-level metrics. It has a default built-in plugin for
hardware monitoring. See Install the Standalone Machine Agent.
JVM Requirements for the Standalone Machine Agent
The Standalone Machine Agent runs on a Java Virtual Machine. JVMs versions 1.5 and higher
are supported for most installations. If you are using AppDynamics Application Analytics, JVM 1.7
is required.
Copyright © AppDynamics 2012-2015 Page 3

The Standalone Machine Agent should work with most, if not all the JVMs supported by the Java
Agent; however, the Standalone Machine Agent is only extensively tested with and fully supported
on Oracle JDK and OpenJDK.
Supported Platforms for Default Hardware Monitor Plugin
Operating Architecture Versions

System
Linux x86 2.2, 2.4, 2.6 kernels
Linux amd64 2.6 kernel
Linux ppc 2.6 kernel
Linux ppc64 2.6 kernel
Linux ia64 2.6 kernel
Linux s390 2.6 kernel
Linux s390x 2.6 kernel
Solaris Sparc-32 2.6, 7, 8, 9, 10
Solaris Sparc-64 2.6, 7, 8, 9, 10
Solaris x86 8, 9, 10
Solaris x64 8, 9, 10
AIX ppc 4.3, 5.1, 5.2, 5.3, 6.1
AIX ppc64 5.2,5.3,6.1
HP-UX PA-RISC 11
HP-UX ia64 11
FreeBSD x86 4.x
FreeBSD x86 5.x, 6.x
FreeBSD x64 6.x
FreeBSD x86,x64 7.x,8.x
OpenBSD x86 4.x,5.x
NetBSD x86 3.1
Mac OS X PowerPC 10.3, 10.4

Mac OS X x86 10.4, 10.5, 10.6
Mac OS X x64 10.5, 10.6
Windows x86 NT 4.0, 2000 Pro/Server, 2003 Server, XP, Vista, 2008
Server, 7
Windows x64 2003 Server, Vista, 2008 Server, 7
The following Linux distributions have been certified:
Distribution Versions
Red Hat 6.2, 7.3, 8.0, 9.0
RHEL 3, 4, 5, 6
CentOS 3, 4, 5
Fedora 2, 3, 4, 5, 6, 7, 8, 9, 10
SuSE 8, 9, 10, 11
Ubuntu 6.06, 8.04, 8.10, 9.04
Debian 2.6, 3.0, 3.1, 3.2, 4.0, 5.0
VMware ESX 2.x, 3.0
XenServer 3.1, 3.2, 4.0, 4.1, 5.0
Slackware 10, 11
Mandrake 10
Scientific Linux 5
Gentoo
Note: If you are using a 64-bit Operating System, use only a 64-bit Java Runtime Environment
(JRE).
Hardware 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.

JVM Memory Requirements
While relatively lightweight, the Standalone Machine Agent adds a certain amount of overhead to
the overall resource consumption of your computer.
AppDynamics recommends allocating the following amounts of additional Heap and PermGen
space to accommodate the agent:
Maximum heap size (-Xmx): 100 MB
Maximum PermGen (permanent generation) heap size (-XX:MaxPermSize): 20 MB
The exact CPU or memory overhead added by the agent can vary depending on the extensions
used and whether the extensions are Java or otherwise. Java extensions would need more heap
space; the amount required depends on how the extension is coded. The Standalone Machine
Agent can run in very little memory, but if you start loading additional extensions, allocate more
heap space 256MB or 512MB just to be safe.
Monitor the memory consumption of the agent to ensure that there are sufficient resource
allocated to it. You may want to enable Garbage Collection logging on the JVM to tune the heap
size for the extensions being used.
CPU Consumption
In terms of CPU consumption, the agent can add anywhere from 0% to 2% additional overhead on
CPU usage, depending on how the extensions are coded and how many extensions are running.
Standalone Machine Agent Architecture

Quick Install for the Standalone Machine Agent
Related pages:
AppDynamics Essentials
Standalone Machine Agent Configuration Properties
Watch the video:
Getting Started with the Standalone Machine Agent
If you downloaded the agent from the AppDynamics download zone, see Install the Standalone
Machine Agent.
1. Confirm you have access to an AppDynamics Controller:

If you use a SaaS controller, AppDynamics sent you the Controller URL and port
number in your Welcome Email.
If you use the on-premise Controller, you supplied the host and port when you
installed the Controller.
2. Log on to the Controller and click the Agent Download Wizard tab.
3. Click Standalone Machine Agent, then click Next.
4. The Controller Location URL window displays the connection info for the Controller as
detected by the download wizard. Confirm and click Next.
5. (Optional) Click SSL to enable SSL encryption between the agent and the Controller. Enter

5.
the SSL port. For AppDynamics SaaS, the SSL port is 443.
6. Log on as an administrator to the machine. Unzip the MachineAgent.zip file.
For example, to unzip the agent on Linux. This is the agent installation directory, <agent
home>:
unzip MachineAgent.zip -d /opt/appdynamics/<agent home>
7. Launch the Standalone Machine Agent.
java -jar <agent home>/machineagent.jar
8. You're ready to begin monitoring.

9. Log on to the Controller to see your application in action.
From here, you can install more agents or you can begin monitoring your application.

Related pages:
Associate Standalone Machine Agents with Applications
Installing the Machine Agent on a PHP Node
Watch the video:
Getting Started with the Standalone Machine Agent
1. Ensure you have Java 1.5 or later installed on the machine. Java 1.7 is required if you want
to use AppDynamics Analytics.
2. Shut down the Standalone Machine Agent process before you install. A machine can have
only one active Standalone Machine Agent installation at a time.
3. Download the Standalone Machine Agent installation zip file.
4. Extract the zip file to the destination directory.
Do not use spaces in the destination directory path.
For Windows environments, unblock the zip file before you extract it as follows:
right-click on the zip file, select Properties, and choose unblock.
5. Configure how the agent connects to the Controller.
Configure properties for the Controller host name and port number using either the
<agent home>/conf/controller-info.xml file or by adding system properties to the JVM
startup script file.
Configure using controller-info.xml: <controller-host>

Configure using System Properties: -Dappdynamics.controller.hostName
Required: Yes
Default: None

Configure using controller-info.xml: <controller-port>
Configure using System Properties: -Dappdynamics.controller.port
Required: Yes
Default: For On-premise Controller installations: Port 8090 for HTTP and 8181 for
HTTPS communication.
For SaaS Controller service: Port 80 for HTTP and port 443 for HTTPS
communication.
If you start a Standalone Machine Agent on a machine that already has a Java Agent
or the PHP Agent installed, the Standalone Machine Agent will automatically associate
itself with the app agent's application, tier, and node settings. If you install an App Agent
for PHP on the same machine as the Standalone Machine Agent, install the App Agent
before the Standalone Machine Agent, and do not specify the tier and node in the
machine agent configuration.
To configure agent to use SSL see Enable SSL for Communicating with the Controller.
To configure the agent to use proxy settings see Proxy Settings for the Controller.
6. (For Multi-tenant mode or SaaS installations only.) Configure the agent account information.
Specify the properties for Account Name and Account Key as provided in the welcome
email sent by AppDynamics Support Team.
Configure using controller-info.xml: <account-name>

Configure using System Properties: -Dappdynamics.agent.accountName
Configure using controller-info.xml: <account-access-key>

Configure using System Properties: -Dappdynamics.controller.hostName
7. Configure the business application, tier, and node.

If an App Agent is installed on the same machine, AppDynamics automatically makes
the association.
If no App Agent is installed on the same machine, specify the application, tier, and node
name where you want the metrics to appear.
Edit the agent <agent home>/conf/controller-info.xml file and specify the following
elements:
Configure using controller-info.xml: <application-name>

Configure using System Properties: -Dappdynamics.agent.applicationName
Configure using controller-info.xml: <tier-name>

Configure using System Properties: -Dappdynamics.agent.tierName
Configure using controller-info.xml: <node-name>

Configure using System Properties: -Dappdynamics.agent.nodeName
If you do not provide configuration details the Standalone Machine Agent will not be
associated with a business application. You can manually associate the agent in the UI

at a later time. See Associate Standalone Machine Agents with Applications.
8. (Optional) Configure the agent to run automatically when the machine starts on Linux or Win
dows.
9. Start the agent.
In a command line console, execute the following command to start the Standalone
Machine Agent:
java -Xmx32m -jar machineagent.jar
Alternatively, in a Linux environment, you can execute the following command in the
background:
nohup java -Xmx32m -jar machineagent.jar &
Note: The agent requires read, write, and delete permission to the <agent home>\conf
and <agent home>\logs directories. Depending on the version of unix and whether
you're using the Sigar or shell script version of the OS monitor, the agent may require
elevated privileges in order to make some system calls to collect metrics.
If your application uses a large number of AppDynamics extensions with the
Standalone Machine Agent, you may need to increase the size of the memory
allocation as follows:
java -Xms64m -Xmx64m -jar machineagent.jar &
10. Verify the agent installation.

Open the <agent home>/logs/machine-agent.log file. If successful, this file should
contain the following message:
Started AppDynamics Machine Agent Successfully
This message is also printed on the STDOUT of the process.
11. Verify that the agent is reporting to the Controller on the Tier Dashboard.
You should see an "up" arrow symbol for the agent in the Machine Agent Status
column.

On this page:

Where to Configure Standalone Machine
Agent Properties
Example Machine Agent controller-info.xml File
Example Startup Configuration Using System Properties
Standalone Machine Agent Properties
Related pages:
Machine Agent FAQ
Where to Configure Standalone Machine Agent Properties
You can configure Standalone Machine Agent properties:

in the controller-info.xml file located in the <machine_agent_home>/conf directory
in the system properties (-D options) section in the JVM start-up script:
java -D<agent_system_properties> -jar <db_agent_home>/machineagent.jar
The system properties override the settings in the controller-info.xml file. Note that the system
properties are case-sensitive.
Example Machine Agent controller-info.xml File
<?xml version="1.0" encoding="UTF-8"?>

<controller-info>
<controller-host>192.10.10.10</controller-host>
<controller-port>8090</controller-port>
<controller-ssl-enabled>false</controller-ssl-enabled>
<enable-orchestration>false</enable-orchestration>
<account-access-key></account-access-key>


<application-name></application-name>
<tier-name></tier-name>
<node-name></node-name>
<force-agent-registration>false</force-agent-registration>
</controller-info>
Example Startup Configuration Using System Properties

A bash example. Note that the system properties are case-sensitive.
-Dappdynamics.controller.hostName=192.168.1.20
-Dappdynamics.controller.port=8090
-Dappdynamics.agent.applicationName=ACMEOnline
-Dappdynamics.agent.tierName=Inventory
-Dappdynamics.agent.nodeName=inventory1 org.tomcat.TomcatServer
Standalone Machine Agent Properties
This section describes the Standalone Machine Agentconfiguration properties, including their
controller-info-xml elements and their system property options.
Agent-Controller Communication Properties
Controller Host Property
Description: This is the host name or the IP address of the AppDynamics Controller, e.g.
192.168.1.22 or myhost or myhost.abc.com. This is the same host that you use to access the
AppDynamics browser-based user interface.
Element in controller-info.xml: <controller-host>
System Property: -Dappdynamics.controller.hostName
Type: String
Default: None
Required: if the Enable Orchestration property is false.
If Enable Orchestration is true, and if the agent is deployed in a compute cloud instance created by
an AppDynamics workflow, do not set the Controller host unless you want to override the
auto-detected value. See Enable Orchestration Property.
Controller Port Property
Description: This is the HTTP(S) port of the AppDynamics Controller. This is the same port that
you use to access the AppDynamics browser-based user interface. If the Controller SSL Enabled
property is set to true, specify the HTTPS port of the Controller; otherwise specify the HTTP port.
See Controller SSL Enabled Property.
Element in controller-info.xml: <controller-port>
System Property: -Dappdynamics.controller.port
Type: Positive Integer
Default: For On-premise installations, port 8090 for HTTP and port 8181 for HTTPS are the
defaults.
For the SaaS Controller Service, port 80 for HTTP and port 443 for HTTPS are the defaults.
Required: Yes, if the Enable Orchestration property is false.
If Enable Orchestration is true, and if the agent is deployed in a compute cloud instance created by
an AppDynamics workflow, do not set the Controller port unless you want to override the

auto-detected value. See Enable Orchestration Property.
Standalone Machine Agent Identification Properties
If the Standalone Machine Agent is installed on a machine that does not have an App Server
agent, configure the application name, tier name and the node name. Otherwise these
configurations are not required for the Standalone Machine Agent.
Account Access Key Property
Description: This is the account access key used to authenticate with the Controller.
Element in controller-info.xml: <account-access-key>
System Property: -Dappdynamics.agent.accountAccessKey
Type: String
Default: None
Required: Yes.
Application Name Property
Description: This is the name of the logical business application that this JVM node belongs to.
Note that 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
Type: String
Defaults: None
Required: If a registered app server agent is already installed on the same host as this machine
agent, this configuration is not required.
Tier Name Property
Description: This is the name of the logical tier that this JVM node belongs to. Note that 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
Type: String
Defaults: None
Required: If a registered app server agent is already installed on the same host as this machine
agent, this configuration is not required.
Node Name Property

Description: This is the name of the JVM node.
Element in controller-info.xml: <node-name>
System Property: -Dappdynamics.agent.nodeName
Type: String
Defaults: None
Required: If a registered app server agent is already installed on the same host as this
Standalone Machine Agent, this configuration is not required.
Multi-Tenant Mode Properties
If the AppDynamics Controller is running in multi-tenant mode or if you are using the AppDynamics
SaaS Controller, specify the account name and account access key for this agent to authenticate
with the Controller.
If the Controller is running in single-tenant mode (the default) there is no need to configure these
values.
When the agent is registered with an AppDynamics SaaS Controller, features used to run Remedi
ation Scripts are disabled If you later reconfigure the agent controller-info.xml to register with a
non-SaaS or on-premise Controller, the agent can run local scripts as usual.
Account Name Property
Description: This is the account name used to authenticate with the Controller.
If you are using the AppDynamics SaaS Controller, the Account Name is provided in the Welcome
email sent by AppDynamics.
Element in controller-info.xml: <account-name>
System Property: -Dappdynamics.agent.accountName
Type: String
Default: None
Required: Yes for AppDynamics SaaS Controller and other multi-tenant users; no for
single-tenant users.
Proxy Properties for the Controller
These properties route data to the Controller through a proxy.
Proxy Host Property
Description: This is the proxy host name or IP address.

Element in controller-info.xml: Not applicable
System Property: -Dappdynamics.http.proxyHost
Type: String
Default: None

Required No
Proxy Port Property
Description: This is the proxy HTTP(S) port.

System Property: -Dappdynamics.http.proxyPort
Type: Positive Integer
Default: None
Required: No
Other Properties
Controller SSL Enabled Property
Description: This property specifies whether the agent should use SSL (HTTPS) to connect to
the Controller. If SSL Enabled is true, set the Controller Port property to the HTTPS port of the
Controller. See Controller Port Property.
Element in controller-info.xml: <controller-ssl-enabled>
System Property: -Dappdynamics.controller.ssl.enabled
Type: Boolean
Default: False
Required: No
Enable Orchestration Property
Description: When set to true, this property enables Standalone Machine Agent workflow task
execution.
It also enables auto-detection of the controller host and port when the app server is a compute
cloud instance created by an AppDynamics orchestration workflow. In a cloud compute
environment, auto-detection is necessary for the Create Machine tasks in the workflow to run
correctly.
See Controller Host Property and Controller Port Property.
The machine agent polls for task executions only when orchestration is enabled.
If the host machine on which this agent resides is not created through AppDynamics workflow
orchestration, this property should be set
to false.
Element in controller-info.xml: <enable-orchestration>
System Property: Not applicable
Type: Boolean
Default: False

Required: No
Force Agent Registration Property
Description: Set to true only under the following conditions:

The agent has been moved to a new application and/or tier from the UI
and
You want to override that move by specifying a new application name and/or tier name in
the agent configuration.
If there is already a registered app server agent installed on the same host as this machine agent,
this override does not work. If you want to override the UI in this case, you must force the agent
registration change from the app server agent configuration.
Element in controller-info.xml: <force-agent-registration>
System Property: Not applicable
Type: Boolean
Default: False
Required: No
Unique Host ID Property
Description: This property logically partitions a single physical host or virtual machine.
You can use the unique host id when you want to use the same node name for multiple nodes on
the same physical machine.
Set the value to a string that is unique across the entire managed infrastructure. The string may
not contain any spaces.
If this property is set on the Standalone Machine Agent, it must be set on the app agent as well.
Note that if more than one app agent is running on the host, to see machine agent metrics it is
necessary to run a new Standalone Machine Agent instance every time you specify a different
unique host id on that host.
System Property: -Dappdynamics.agent.uniqueHostId
Type: String
Default: None
Required: No
Install the Standalone Machine Agent as a Windows Service

On this page:
Install the Standalone Machine Agent as a Windows
Service - Pre Windows 2008
Install the Standalone Machine Agent as a Windows

Service - Windows 2008 and 2012
Uninstall the Standalone Machine Agent as a Service
Known Issues
Most Windows server software runs as a service when the machine boots up. To secure your
environment and ensure Standalone Machine Agent availability, you can install the Standalone
Machine Agent as a Windows service using the SRVANY.EXE and SC.EXE utilities that are part of
the Microsoft Resource Kit for Windows 2003 Server. The SRVANY.EXE tool creates a Windows
service that launches the JVM processes for the agent in non-GUI mode using parameters
specified in the registry of the service. The SC.EXE command is used to install and uninstall the
agent service.
Install the Standalone Machine Agent as a Windows Service - Pre Windows 2008
The following procedure involves editing the registry. Before proceeding, know how to backup
and restore the registry as described in the WIndows Registry Editor online help.
1. Install the agent as usual, described in Install the Standalone Machine Agent.
2. Obtain the INSTSRV.EXE and SC.EXE utilities.
Download the Windows Server 2003 Resource Kit Tools, at http://www.microsoft.com/en-us/
download/details.aspx?id=17657. The required utilities are included in this resource kit
3. Prepare registry and batch command files.
To simplify service creation and deregistration, we have attached two batch command files
to this page, InstallService.cmd and UninstallService.cmd. InstallService.cmd requires the
information in the MachineAgent.reg file to set the registry key for the service.
MachineAgent.reg to set the registry key values for the service
InstallService.cmd to install the service
UninstallService.cmd to uninstall the service
Download these files and edit them as indicated below. Specify the same service
name in all three files.
a. Customize MachineAgent.reg
Edit the service name, Application, AppParameters, and AppDirectory values of this
file for your environment.
Specify the service name on the first line of this file.
AppDynamics Machine Agent Service in the sample file attached.
Application is the path to the JDK you use for Standalone Machine Agent.
d:\\AppDynamics\\MachineAgent\\jre6\\bin\\java.exe in the
sample above.
AppParameters is everything you want to pass to the JVM as arguments.
-jar MachineAgent.jar in the sample attached.
AppDirectory points to the agent working directory.
d:\\AppDynamics\\MachineAgent in the sample attached.
b. Customize InstallService.cmd
Edit the create and binPath values in this file for your environment.
Specify the service name in quotes in the sc command create option as follows:

b.
sc create "AppDynamics Machine Agent Service"

Specify binPath as the path to the SRVANY.EXE Windows Resource
d:\AppDynamics\MachineAgent\srvany.exe in the sample attached
The service installed runs with the permissions of the user logged in
when service is created. To change the user running the installed
process, modify InstallService.cmd by inserting the following anywhere
before "pause" at the end of the file.
sc config <service> obj= <username> password=
<password>
Note: There is a required space between obj= and <username> .
c. Customize UninstallService.cmd
Specify the name of the service in quotes after the sc stop or delete options.
"AppDynamics Machine Agent Service" in the sample attached.
4. From the Windows Explorer, right-click InstallService.cmd and click Run as Administrator.
Install the Standalone Machine Agent as a Windows Service - Windows 2008 and 2012
1. Download NSSM - the Non-Sucking Service Manager.

2. Create a start.bat file containing your agent startup script, such as:
java -jar machineagent.jar
3. Add the path to nssm.exe to your Path environment variable.
4. Start a command shell and enter the following:
nssm.exe install <service name>
where <service name> is the name of the agent service.
5. In the NSSM service installer dialog, enter the full path to the agent startup script in the Path
field of the Application tab. Enter any other details appropriate for your environment. For
information on the various options, see the NSSM documentation.
6. Click Install service.
A service is created named <service name>, that starts up automatically when the machine is
started and that is also restarted if the process stops for any reason.
Uninstall the Standalone Machine Agent as a Service
If you used INSTSRV.EXE and SC.EXE utilities:
From the Windows Explorer, right-click UninstallService.cmd and click Run as Administrator.
This stops and removes the service from Windows.
If you used NSSM:
From a command shell, enter
nssm.exe remove <service name>
where <service name> is the name of the agent service.
Known Issues
In Windows Server 2003 you must install and start or stop the service from the console window. If

you do a normal RDP connection to the 2003s Terminal Services the service, will be stopped
when you log-out. Therefore, issue the command "mstsc /console <machinename>" to connect to
the console session of Windows Server 2003.
Deploy Multiple Standalone Machine Agents

On this page:
Deploy the Standalone Machine Agent
Deploy Multiple Agents from a Common Directory
Deploy the Standalone Machine Agent
1. Download the latest Standalone Machine Agent ZIP file from http://download.appdynamics.com/
.
2. Unzip the downloaded file on the destination machine in the desired directories.
3. Modify the <agent home>/conf/controller-info.xml files to set the application name, tier name,
node name, Controller host and Controller port properties. The -D settings allowed for Standalone
Machine Agent are not the same as those for Java Agent. The only one supported,
agent.runtime.dir is described below.
4. Configure the startup script for the machine to start the Standalone Machine Agent every time
the machine reboots. For example, you could add the machine startup command to .bashrc.
To handle large values for metrics, run the Standalone Machine Agent using a 64-bit JDK.
Deploy Multiple Agents from a Common Directory
If you want to deploy your agents from a common directory, such as an NFS mounted, shared
directory, you can launch the Standalone Machine Agent installation executable from multiple
servers which have access to the same NFS mounted, shared directory.
All properties common to the Standalone Machine Agents can be in the controller-info.xml file,
such as controller host, controller post, and account name.
Properties unique to each Standalone Machine Agent such as app name, tier name, node name
and log directory must be provided with -D parameters in the JVM startup script on each machine
that is running the Standalone Machine Agent such as the following:
JVM startup properties

java -Dappdynamics.agent.runtime.dir=<your_custom_log_dir>
-Dappdynamics.agent.applicationName=xyz -Dappdynamics.agent.tierName=123
-Dappdynamics.agent.nodeName=abc -jar machineagent.jar
You can use either of the following methods to specify where the log files for the agent should be
stored.

Add a Property to the JVM Startup Script
Add the following system property to the system properties of the JVM startup script for
the Standalone Machine Agent:
-Dappdynamics.agent.runtime.dir=<$Absolute-path-to-local-logs-directory>
Add an Element to controller-info.xml
Add the agent.runtime.dir element to specify the absolute path to the local logs directory
the <machine agent install directory>/conf/controller-info.xml file, but in this case you must also
edit the agent installation\logs\log4j.xml file to provide the absolute path to the local logs directory
as follows:
Example log4j.xml entry

<appender name="FileAppender"
class="com.singularity.ee.agent.systemagent.SystemAgentLogAppender">
<param name="File" value="/opt/mypath/logs/agent.log"/>
<<<<<<<<<<<<<<<<<<<<<<<PATH TO LOCAL LOGS DIR HERE
<param name="MaxFileSize" value="5000KB"/> <param name="MaxBackupIndex"
value="5"/>
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d{ABSOLUTE} %5p [%t] %c{1}:%L -
%m%n"/>
</layout>
</appender>
Configure Multiple Standalone Machine Agents for One Machine for Java
On this page:
Configuring Multiple Standalone Machine Agents
Sample Configuration
Related pages:
Java Agent Configuration Properties
If you have different applications running on the same machine, to get hardware metrics for each
application, run separate Standalone Machine Agents on the same machine.
To do this, create multiple copies of the Standalone Machine Agent. Then configure each
Standalone Machine Agent / app agent pair to use the same applicationName and uniqueHostId.

The uniqueHostId makes it appear to the Controller that the application is running on different
machines. See Application Name Property and Unique Host ID Property.
The uniqueHostId property is required when multiple Standalone Machine Agents are run on same
machine or host.
When an app agent runs on the same machine as a machine agent, configure the same
uniqueHostId property value on for both the app agent and the machine agent. If there are multiple
app agent/machine agent pairs on the same host, each pair should have a different uniqueHostId
property.
When different tiers in the same application are associated with different machine agents,
configure a different uniqueHostId property for each app agent-tier/machine agent pair.
To retain historical data if the nodes are moved to a different machine, use the hostname of the old
machine from which the nodes were moved as the UniqueHostId parameter when you configure
the app agent/machine agent pair on the new host. For example, if the hostname of the original
machine was "12345.sample.com", on the new host start the app agent and the machine agent
with:
-Dappdynamics.agent.uniqueHostId=12345.sample.com
Configuring Multiple Standalone Machine Agents
The following instructions assume two applications and two standalone machine agents on a
single machine, but they can be interpolated to cover more than two.
To configure two Standalone Machine Agents for two applications running on the same machine
1. Download two copies of the Standalone Machine Agent, one for each application.
2. Assign the standalone machine agents different names, for example: "MachineAgent1" and
"MachineAgent2".
If there are custom scripts running on the standalone machine agents, they must not use the
same resources.
3. Configure the first application/machine agent pair for the first application:
a. Delete the app agent node from the Controller UI.
b. Configure the applicationName and uniqueHostID properties for the app agent.
c. Configure the applicationName and uniqueHostID properties for the machine agent
using the same application name and unique host id values that you used for the app
agent configuration.
4. Configure the second application/machine agent pair for the second application:
a. Delete the app agent node from the Controller UI.
b. Configure the applicationName and uniqueHostID properties for the app agent. These
values must be different from the values used for the first application.
c. Configure the applicationName and uniqueHostID properties for the Standalone
Machine Agent using the same applicationName and uniqueHostId values that you

c.
used for the app agent configuration.

5. Restart all JVMs.
Sample Configuration
The following image shows a sample configuration of two physical machines with two applications
each. In it:
Machine1 runs App1, which is instrumented with one app agent (AppAgent1) and one
Standalone Machine Agent (MachineAgent1).
Machine1 also runs App2, which is instrumented with one app agent (AppAgent2) and one
Machine2 runs App1, which is instrumented with one app agent (AppAgent3) and one
Machine2 also runs App2 is instrumented with one app agent (AppAgent4) and one
Given this deployment, the Controller would report separate metrics for each of Machine1_App1,
Machine1_App2, Machine2_App1, and Machine2_App2.
Resolve Installation Problems

On this page:
Verify that the Agent is Running
Resolve Agent Connectivity Problems
Related pages:
Machine Agent FAQ
Verify that the Agent is Running
Use the following command to verify that the agent process is running:
Linux:

ps -ef | grep machine
Windows:
1. Open a command line console.
2. Start the Task Manager and click the Processes tab.
3. The agent process should be running. If it is not running, stop and then restart the agent
Resolve Agent Connectivity Problems
If when you start the Standalone Machine Agent, it cannot register with the controller or associate
with the same node in the Controller, the stack trace may reveal the reason why.
For example, the following message in the stack trace may indicate that the application, tier, and
node information was not provided during the Standalone Machine Agent startup command or in
the controller-info.xml file.
<execution-output>System agent 239590 not associated with application, metric

registration request refused.</execution-output>
Make sure you have configured the application, tier, and node information either in the
agent startup command or in the controller-info.xml file.
After configuring, restart the agent and check the behavior. Standalone Machine Agent log files
may also provide some insight into problems.
Start the Standalone Machine Agent Automatically on Linux

Related pages:
1. Create an initialization script that starts the Standalone Machine Agent agent, as in the
sample initialization script that is an attachment to this page.
In your script, set the JAVA and AGENT_HOME values to the paths for your system. Also
configure agent options, as needed.
2. Enable execution permissions for the script. For example, given an initialization script
named machineagent, enter:
sudo chmod 775 machineagent
3. Place the script in the initialization directory on your system, typically /etc/init.d. Alternatively,
create a symbolic link to the script from the init.d directory to the script if you want to keep it in
another location.
4.

4. Add the script as a service as follows:
On Red Hat and most Linux Operating Systems, run these commands, replacing "mac
hineagent" with the name of your file or symbolic link:
chkconfig --add machineagent

chkconfig --level 2345 machineagent on
On Ubuntu and Debian Operating Systems, run this command, replacing "machineag
ent" with the name of your file or symbolic link:
update-rc.d -f machineagent start 99 2 3 4 5 .
In the command:
start is the argument given to the script (start, stop).
99 is the start order of the script (1 = first one, 99 = last one)
2 3 4 5 are the runlevels to start
Be sure to include the dot (.) at the end of the command.
The Standalone Machine Agent now starts automatically upon machine startup.
Start the Standalone Machine Agent Automatically on Windows

Related pages:
1. Create a batch file containing the following line:
java -Xms32m -jar <agent home>/machineagent.jar
If your application uses a large number of AppDynamics extensions with the Standalone
Machine Agent, you may need to increase the size of the memory allocation as follows:
java -Xms64m -jar <agent home>/machineagent.jar
2. Click Control panel -> Scheduled Tasks.

3. Select the batch file to execute. This is the file created in step 2.
4. Create a new task.
5. Select When my computer starts.
6. Enter the administrator's credentials to run the Standalone Machine Agent as that user.
7. Click Finish.
8.

8. To start the Standalone Machine Agent for the first time, right-click on the scheduled task,
and click Run.
Associate Standalone Machine Agents with Applications

On this page:
Associate a Standalone Machine Agent with One
Business Application
Associate Multiple Agents with Multiple Business
Applications
Associate one Agent with Multiple JVMs
If no configuration details are provided during installation, or if the node has been moved to
another application, then the Standalone Machine Agent appears in the System -> Agents tab as
"not associated with any applications". To have the Standalone Machine Agent start sending
metrics to a tier or executing workflow tasks, manually associate it with an application.
The following message in the agent log (< agent home>/logs/machine-agent.log) indicates that
there is no application associated with the agent:
Received Metric Registration request for a machine id:<NNNNN> that is NOT

registered to any nodes yet, sending back null response!
Associate a Standalone Machine Agent with One Business Application
If an App Agent is installed on the same machine, AppDynamics automatically makes the
association. However, if there is no App Agent on the machine and you haven't specified the
app/tier/node properties in the controller.xml file, you can set them in the UI as follows:
1. In the AppDynamics Agents window, select a Standalone Machine Agent.
2. Click Associate with an Application.
Associate Multiple Agents with Multiple Business Applications
If the machine is hosting servers that belong to multiple business applications, you may need
multiple agents.
If there are nodes belonging to multiple business applications, you can run multiple agents each
configured to report metrics for a different node, tier, and application.
You cannot "assign" a single Standalone Machine Agent to multiple business application per se.
A Standalone Machine Agent on a specific machine is automatically associated with all nodes
running on that machine. A node is associated with a single business application. Therefore an
application is associated with the agents of its nodes. By default a Standalone Machine
Agent inherits the application/tier/node names of the App Agent installed on the same hardware.
Associate one Agent with Multiple JVMs
If you have an application where a tier has three nodes, each running on a separate VM on the

same machine and you want the Standalone Machine Agent to report the metrics for their host
machine to each node do the following
1. Stop the agents for all app agent nodes and the machine agent node associated with the
application. If this is is fresh application association ignore this step.
2. Start the appserver agent node for each VM (using the app, tier and node details provided in
<agent home>/conf/controller-info.xml) with the -D JVM arg, in addition to the -javaagent
argument as below .
-Dappdynamics.agent.uniqueHostId=myTierAHostName1 -javaagent
3. Start the Standalone Machine Agent with same uniquehostid used for agent nodes
associated above.
java -Dappdynamics.agent.uniqueHostId=myTierAHostName1 -jar machineagent.jar
Ensure sure you have not provided application-name, tier-name, and node-name details in
<agent home>/conf/controller-info.xml file.
Metrics Collected by the Standalone Machine Agent

On this page:
Accessing Hardware Metrics
Customize Default Metrics
Adding Custom Metrics
Related pages:
Machine Agent FAQ
Watch the video:
Standalone Machine Agent: An Overview
The Standalone Machine Agent automatically collects and displays CPU, Memory, Disk, and
Network metrics on the Node Dashboard Hardware tab. There are many more metrics collected
which you can view in the Metric Browser > Application Infrastructure Performance >Hardware
Resources or add them to your Custom Dashboard. To add CPU metrics to your Custom
Dashboard, add the metrics for only one node per server. Metrics collected for a node associated
with the Standalone Machine Agent are for the entire server hosting that node. The Standalone
Machine Agents reports metrics and hardware usage data to the Controller once a minute.
CPU Utilization: Average, minimum, and maximum values in percentage for CPU Busy Time
for the selected point in the graph.
Memory Utilization: Average, minimum, and maximum values in KB for Memory Used for the
selected point in the graph.
Disk I/O: Average, minimum, and maximum values for data (KB) written/sec for the selected
point in the graph.
Network I/O: Average, minimum, and maximum values for outgoing data in KB/sec for the

selected point in the graph.
Accessing Hardware Metrics

You can view hardware metrics from the Hardware tab of the Node Dashboard if a Standalone
Machine Agent is installed on the machine that hosts the node.
You can also view hardware metrics in the Metric Browser in the Hardware Resources branch of
a tier.
Customize Default Metrics

You can eliminate some of the default disk backup metrics collected by the Standalone Machine
Agent and enable collection of metrics for virtual disks and external network traffic.
Adding Custom Metrics

You can add script-based and Java-based custom monitoring extensions.
You can send metrics to the Standalone Machine Agent using its HTTP listener.
For a more complete discussion of adding custom metrics, see Extensions and Integrations.
Configure Metrics for Virtual Disks and External Network Traffic
By default, the Standalone Machine Agent reports metrics for only network mounted and local
disks. Also, only the external network traffic is aggregated (to ensure backward compatibility with
previous versions of AppDynamics).
However, you can customize this default behavior by modifying the auto-generated configuration
file, task-template.xml. The task-template.xml file provides information about the current
configuration of the Standalone Machine Agent.
To customize default Standalone Machine Agent metric collection
Step 1: Open the task-template.xml file.

AppDynamics creates this file in the <agent home>/monitors/JavaHardwareMonitor/ directory
when the Standalone Machine Agent starts up for the first time and discovers the disks and
network hardware the agent can monitor on the machine where it is installed.
Step 2: Modify the task-template.xml file.
A sample task-template.xml file is given below:

<config>
<disk aggregate="false" enabled="false">sunrpc</disk>
<disk aggregate="true" enabled="true">/dev/sdb1</disk>
<disk aggregate="false" enabled="false">proc</disk>
<disk aggregate="false" enabled="false">none</disk>
<disk aggregate="false" enabled="false">devpts</disk>
<disk aggregate="true" enabled="true">/dev/sda1</disk>
<disk aggregate="false" enabled="false">nfsd</disk>
<disk aggregate="true" enabled="true">/dev/mapper/saas4-binlog</disk>
<disk aggregate="false" enabled="false">sysfs</disk>
<disk aggregate="false" enabled="false">tmpfs</disk>
<network aggregate="true" enabled="true">lo</network>

<network aggregate="true" enabled="false">sit0</network>
<network aggregate="true" enabled="true">eth0:1</network>
<network aggregate="true" enabled="true">eth0</network>
<network aggregate="true" enabled="false">eth1</network>
</config>
To enable aggregation operation for localhost (lo) network metrics, change the value of the
aggregate attribute (for the network element "lo") to "true".
To enable monitoring for a virtual disk, set the value of the enabled attribute to "true" for that
disk.
Step 3: Rename the task-template.xml file to task.xml.
It is important to rename the task-template.xml file (else it will be overwritten by Machine
Agent). The task-template.xml file is automatically generated by the Standalone Machine
Agent.
If you want the Standalone Machine Agent to monitor a special device that is not enabled,
add a file named "task.xml" in the <agent home>/monitors/JavaHardwareMonitor/ directory.
The format of the task.xml file must be exactly the same format aa the task-template.xml file.
Not all disks and networks have to be listed in task.xml. If the machine agent finds a disk or
a network that is not listed in task.xml, default properties are applied.
Step 4: Restart the Machine Agent.
Restart the machine agent for the changes to take effect.
Limit Disk Backup Metrics Collection

On this page:
Switch from the Java Hardware Monitor to the Hardware
Monitor
By default, the Standalone Machine Agent uses the Java Hardware Monitor (Sigar API-based),
which may collect more metrics than you need.
For example, you may not want to see backup metrics such as the following, where out of a total
3315 metrics reported by the Standalone Machine Agent, 2584 are due to back up disk metrics :

Instead of using the default Java Hardware Monitor the Standalone Machine Agent can use the
Hardware Monitor which uses an OS specific script file (linux-stat.sh in this case) to capture stats,
which will not track backup porcesses.
To stop tracking backup process and limit future disk metrics switch from the Java Hardware
Monitor to the Hardware Monitor.
Switch from the Java Hardware Monitor to the Hardware Monitor
1. Stop the Standalone Machine Agent by stopping its process. See below for info on
identifying the agent process.
2. Switch from the Java Hardware Monitor to Hardware Monitor as follows:
a. Open for edit monitor.xml from <Agent install
directory>/monitors/HardwareMonitor/monitor.xmll
b. Change <enabled>false</enabled> to <enabled>true</enabled> and then save the
file.
c. Open for edit <Agent install directory>/monitors/JavaHardwareMonitor/monitor.xml.
d. Change <enabled>true</enabled> to <enabled>false</enabled> and then save the
file.
3. Restart the Standalone Machine Agent.
From the command line, enter java -jar <Agent install directory>/machineagent.jar.
This limits the future disks metrics but will not delete the existing metrics.
Configure Custom Metrics for the z-OS Machine Agent

On this page:
Start the Resource Management Facility (RMF)
Related pages:
Instrument JVMs in a Dynamic Environment
This topic describes how to configure custom metrics in a z-OS environment.
Start the Resource Management Facility (RMF)
AppDynamics requires the RMF (Resource Management Facility) to collect the data for the

required metrics.
Initialize and start the RMF
1. Connect to the EPTDFRH user and initialize the ETPGZCK user, if not already done.
2. Connect to TSO and provide the details of IBMUSER.
3. Upon a successful connection, choose the SD (System Display and Search Facility) optio
n.
4. Use the following commands to initialize and start the RMF:
/S RMF
/F RMF,START III
/S GPMSERVE,MEMBER=01
5. Access the following URL to confirm the RMF startup:
http://192.86.32.72:8803/
After successful RMF startup, the URL should display a valid HTML page.
6. Click Explore and then Metrics to display all the available metrics for SVSCPLEX,
SYSPLEX.
Install the scripts
1. Download and unzip the attached zos-machine-agent.zip file to the <machine-agent install
directory>/monitors/ directory.
2. Select the required metric locations, and add them to urls.list file in the zos-monitor
directory. For example:

% CPU utilization =
http://192.86.32.72:8803/gpm/perform.xml?resource=S0W1,*,PROCES
SOR&id=8D0460
% users =
http://192.86.32.72:8803/gpm/perform.xml?resource=%22,SVSCPLEX,
SYSPLEX%22&id=8D0D50
% using for i/o by MVS image =
SYSPLEX%22&id=8D1DA0
% CSA utilization by MVS image =
SYSPLEX%22&id=8D2410
% users by MVS image =
SYSPLEX%22&id=8D0D60
Confirm that the scripts are successful
Once the above steps are performed successfully, start the Standalone Machine Agent in debug
mode.
The following information in the Standalone Machine Agent log confirms that the processing is
successful.
[Worker-7] 28 Mar 2012 19:59:02,128 INFO ExecTask - Started Executable Command

[[G:\AppDynamics\64bit\3.3.4\
MachineAgent-3.3.4.0RC\monitors\CustomMonitor\metrics.bat]]
[Worker-7] 28 Mar 2012 19:59:02,128 DEBUG ExecTask - Will wait for process exit
, before sending execution status.
[Worker-1] 28 Mar 2012 19:59:04,651 DEBUG MonitorOutputHandler - Monitor line
parsed:name=Custom Metrics|zos|% CPU utilization (CP), value=3
[Worker-1] 28 Mar 2012 19:59:04,653 DEBUG MonitorOutputHandler - Reporting
metric after reading metric [Custom Metrics|zos|% CPU utilization (CP)]
[Worker-1] 28 Mar 2012 19:59:04,653 DEBUG MonitorOutputHandler - Reporting
Metric Name [Custom Metrics|zos|% CPU utilization (CP)] Value [3]
[Worker-7] 28 Mar 2012 19:59:04,654 DEBUG ExecTask - Process exited with code: 0
Extensions and Custom Metrics

On this page:
Add New Custom Metrics
Types of Monitoring Extensions
Delete Custom Metrics
Related pages:
Build a Monitoring Extension Using Scripts

Build a Monitoring Extension Using Java
Standalone Machine Agent HTTP Listener
Extensions and Integrations
Watch the video:
Standalone Machine Agent - Overview of Custom
Extensions
Using the Standalone Machine Agent, you can supplement the existing metrics in the
AppDynamics Controller UI with your own custom metrics. There are many extensions currently
available on the AppSphere Community site. Some are created by AppDynamics and some have
been created by users.
Like built-in metrics, your custom metrics are subject to the following AppDynamics features:
automatic baselines and anomaly detection
availability for display on custom dashboards
availability for use in policies
visibility of all metrics in the Metric Browser, where you can display external metrics along
with AppDynamics metrics on the same graph
Add New Custom Metrics

To create custom metrics, you create a monitoring extension. In your extension, you define the
name and path of your metric (where it appears in the metric browser tree), what type of metric it is
(sum, average, and so on), and how the data for the metric should be rolled up as it ages. One
agent can run many extensions, although you may need to increase the amount of memory for the
agent JVM if you do. You can even have multiple copies of the same extension, if they are in
different directories.
A custom metric can be common across nodes or associated with a specific tier. When you create
a metric, you specify the path in which it will appear in the metric tree. To make a common custom
metric, use the root tree path Custom Metrics in your metric declaration. To make a tier-specific
metric, specify the metric path associated with that component. For details, see the topics on
creating Java or script-based custom metrics listed below.
Types of Monitoring Extensions

You can implement custom metrics using the following mechanisms.
Using a script: You can write a shell script (LINUX) or batch file (Windows) to report custom
metrics every minute to the Standalone Machine Agent. The Standalone Machine Agent
passes these metrics on to the Controller.
For more information, see Build a Monitoring Extension Using Scripts.
Using Java: Your custom metrics may be too complicated to collect using a script. For
example, you may need to perform complex calculations or call a third party API to get the
metrics. In this case you can extend the JavaServersMonitor class to collect the metrics and
report them to the Standalone Machine Agent. Your Java program extends the

JavaServersMonitor class to provide your custom functionality.
See Build a Monitoring Extension Using Java.
Using HTTP: If you enable the agent HTTP listener, you can post HTTP requests to the
Standalone Machine Agent to send it custom metrics every minute. This is done by starting
the Standalone Machine Agent with a Jetty HTTP listener.
See Standalone Machine Agent HTTP Listener for information on starting the HTTP listener
and sending it metrics.
Delete Custom Metrics

Once you establish a metric, you can not delete it without access to the Controller database
(on-prem) and cannot delete it (on SAAS). If you need to delete a metric, please contact
AppDynamics Support for assistance.

On this page:
Before You Begin
Process for Creating a Monitoring Extension Using
Scripts
Metric Processing Qualifiers
Adding a Monitoring Extension
Example: Create a monitoring extension for open files
Related pages:
Configure Health Rules
Alert and Respond
Remediation Actions
Watch the video:
Standalone Machine Agent - Overview of Custom Extensions -
1:06
Direct Link: https://player.vimeo.com/video/110812089
You can write a monitoring extension script (also known as a custom monitor or hardware monitor)
to add custom metrics to the metric set that AppDynamics already collects and reports to the
Controller. Your script reports the custom metrics every minute to the Standalone Machine Agent.
The Standalone Machine Agent passes these metrics to the Controller.
This topic describes the steps for adding custom metrics using a shell script and includes an
example.
Before You Begin

Before creating your own extension from scratch, look at the extensions that have been created
and shared among members of the AppDynamics community. The extensions are described and
their source is available for free download at:
https://github.com/Appdynamics/
New extensions are constantly being added. It is possible that someone has already created
exactly what you need or something close enough that you can download it and use it after making
a few simple modifications.
Process for Creating a Monitoring Extension Using Scripts
To create a monitoring extension using scripts:

1. Create your script. See Create the script.
2. Create a monitor.xml configuration file. See Create the monitor.xml file.
3. Create a zip file containing these two files plus any dependent jar files.
4. Create a subdirectory (<your_extension_dir>) in <agent home>/monitors.
5. Unzip the zip file into <agent home>/monitors/<your_extension_dir>.
Required Agent Properties

Ensure that you have correctly configured the agent in the controller-info.xml file and
on the agent start command on the command line. For information on configuring
required and optional agent properties, see Database Agent Configuration Properties
.
6. Restart the Machine Agent.
Metric Names
Metric names must be unique within the same metric path but need not be unique for the entire
metric hierarchy.
It is a good idea to use short metric names so that they will be visible when they are displayed in
the Metric Browser.
Prepend the metric path to the metric name when you upload the metrics to the Controller.
Metric Processing Qualifiers
The Controller has various qualifiers for how it processes a metric with regard to aggregation, time
rollup and tier rollup.
There are three types of metric qualifiers:
Aggregation qualifier
Time roll-up qualifier
Cluster roll-up qualifier
In the script, specify the metric qualifiers after the name-value pair for the metric.
A typical metric entry in the script file has the following structure:

name=<metric name>,value=<long value>,aggregator=<aggregator type>,
time-rollup=<time-rollup strategy>, cluster-rollup=<cluster-rollup
strategy>
Aggregation Qualifier
The aggregator qualifier specifies how the Standalone Machine Agent aggregates the values
reported during a one-minute period.
Specify the aggregation qualifier as aggregator="aggregator type"
This value is an enumerated type. Valid values are:
Aggregator Description
Type
AVERAGE Default. Average of all reported values in that minute.
SUM Sum of all reported values in the minute, causes the metric to behave like a
counter.
OBSERVATION Last reported value in the minute. If no value is reported in that minute, the
last reported value is used.
Time Roll Up Qualifier
The time-rollup qualifier specifies how the Controller rolls up the values when it converts from
one-minute granularity tables to 10-minute granularity and 60-minute granularity tables over time.
The value is an enumerated type. Valid values are:
Roll up Description
Strategy
AVERAGE Average of all one-minute values when adding it to the 10-minute granularity table;
average of all 10-minute values when adding it to the 60-minute granularity table.
SUM Sum of all one-minute values when adding it to the 10-minute granularity table;
sum of all 10-minute values when adding it to the 60-minute granularity table.
CURRENT Last reported one-minute value in that 10-minute interval; last reported ten-minute
value in that 60-minute interval.
Cluster Rollup Qualifier
The cluster-rollup qualifier specifies how the Controller aggregates metric values in a tier (a
cluster of nodes).

The value is an enumerated type. Valid values are:
Roll up Description
Strategy
INDIVIDUAL Aggregates the metric value by averaging the metric values across each node
in the tier.
COLLECTIVE Aggregates the metric value by adding up the metric values for all the nodes in
the tier.
For example, if a tier has two nodes, Node A and Node B, and Node A has 3 errors per minute
and Node B has 7 errors per minute, the INDIVIDUAL qualifier reports a value of 5 errors per
minute and and COLLECTIVE qualifier reports 10 errors per minute. INDIVIDUAL is appropriate
for metrics such as % CPU Busy where you want the value for each node. COLLECTIVE is
appropriate for metrics such as Number of Calls where you want a value for the entire tier.
Adding a Monitoring Extension
Step 1. Create a directory under the Standalone Machine Agent monitors directory
The <agent home>\monitors directory is the repository for all monitoring extensions. For each new
extension, create a sub-directory under the /monitors directory. The user running the agent
requires read, write, and execute permissions to this sub-directory.
For example, to create a monitoring extension that monitors open files in the JVM, create a
sub-directory named "openfiles" under the <machine agent home/monitors> directory.
Step 2. Create the script file
A script writes data to STDOUT. The Standalone Machine Agent parses STDOUT and sends
information to the Controller every minute. Use the following instructions to create the script file.
1. Specify a name-value pair for the metrics.

1.
Each metric has a name-value pair that is converted to a java 'long' value. A typical metric
entry in the script file has the following structure:
name=<metric name>,value=<long value>,aggregator=<aggregator

type>, time-rollup=<time-rollup strategy>,
cluster-rollup=<cluster-rollup strategy>
Use the following format:
Format
Standard Form Hardware Resources| Instrument Name=Instrument Value
Fully Qualified Form Hardware Resources| <metric name>,value=<long value>
2. Define the category of the metric, for example:

Infrastructure (for the default hardware metrics, see Metrics Collected by the
Standalone Machine Agent)
JVM (for the default metrics, see Monitor JVMs)
Custom Metrics
Custom metrics must have the path prefixes:
Custom Metrics
Server|Component:<id>
Metrics with the Custom Metrics prefix are common across all tiers in your application.
Metrics with the Server|Component:<id> prefix appear only under the specified tier.
To discover the component ID of a tier, select the tier from the Controller UI application tree.
The component ID appears in the URL of the browser.
The "|" character separates the branches in the metric hierarchy, telling the Controller where
the metric should appear in the metric tree:

Custom Metrics|Hardware Resources|Disks|Total Disk Usage %
Custom Metrics|Hardware Resources|Disks|Disk 1|Current Disk
Usage %
You can insert a custom metric alongside an existing type of metric. For example, the
following declaration causes the custom metric named pool usage to appear alongside the
JMX metrics:
Server|Component:18|JMX|Pool|First|pool usage
The metric can then be used in health rules as would other types of JMX metrics.
To monitor multiple metrics with the same script file, have the script write a different line for
each one to STDOUT, such as the following:
name=Custom Metrics|Hardware Resources|Disks|Total Disk Usage %,

value=23
name=Custom Metrics|Hardware Resources|Disks|Disk 1|Current Disk
Usage %, value=56
Step 3. Copy the script file to the directory created in Step 1
Ensure that the agent process has execute permissions not only for the script file but also for the
contents of the file.
Step 4. Create the monitor.xml file
1. For each custom monitor create a monitor.xml file.

The monitor.xml file executes the script file created in Step 2. You can edit the following
sample file to create your file.

<monitor>
<name>HardwareMonitor</name>
<type>managed</type>
<description>Monitors system resources - CPU, Memory,
Network I/O, and Disk I/O.</description>
<monitor-configuration> </monitor-configuration>
<monitor-run-task>

<execution-style>continuous</execution-style>
<name>Run</name>
<type>executable</type>
<task-arguments></task-arguments>
<executable-task>
<type>file</type>

<file os-type="linux">linux-stat.sh</file>
<file os-type="mac">macos-stat.sh</file>
<file os-type="windows">windows-stat.bat</file>
<file os-type="solaris">solaris-stat.sh</file>
<file os-type="sunos">solaris-stat.sh</file>
<file os-type="aix">aix-stat.sh</file>
</executable-task>
</monitor-run-task>
</monitor>
The os-type attribute is optional for the executable-task file element when only one os-type
is specified. One monitor.xml file executes one script per os-type.
2. Select the execution style from one of the following:
Execution Description Example

Style
continuous Choose "continuous", if you while [ 1 ]; do

want data collection averaged ... the actual script goes here ...
over time. sleep 60
(For example: Averaging CPU done
over minute).
This ensures that the script
keeps running until the
Standalone Machine Agent
process is terminated.(!) For the
monitor to be declared as
'continuous', the script should
also run in an infinite loop.

periodic Choose periodic, if you want
<execution-style>periodic</execution-style>
data to be reported from
<execution-frequency-in-seconds>30</execution
system performance counters <execution-timeout-in-secs>30</execution-time
periodically. The periodic task
runs every minute by default
and the data is aggregated.
If you want the periodic task to
run with any other frequency,
specify the
execution-frequency-in-seconds
parameter. The execution
frequency must be less than
60.
For periodic execution style,
you can also specify the
frequency and timeout
parameters. For example:
3. Add the name of this script file to the <file> element in the monitor.xml file. Be sure to use
the correct os-type attribute. The os-type value should match the value returned from
calling System.getProperty("os.name"). See http://docs.oracle.com/javase/1.5.0/docs/api/jav
a/lang/System.html#getProperties%28%29(opens in new window).
<file os-type="your-os-type">{script file name}</file>
You can use either the relative or absolute path of the script.
Step 5. Copy the monitor.xml file to the directory created in Step 1
Step 6. Restart the Standalone Machine Agent
Required Agent Properties

Ensure that you have correctly configured the agent in the controller-info.xml file and on the
agent start command on the command line. For information on configuring required and
optional agent properties, see Database Agent Configuration Properties.
After restarting the Standalone Machine Agent, you should see following message in your log file:
Executing script [<script_name>] on the console to make sure your

changes work with the machine agent.
Step 7. Verify execution of the monitoring extension script

To verify the execution of extension, wait for at least one minute and check the metric data in the
Metric Browser.
You can now create alerts based on any of these metrics.
Example: Create a monitoring extension for open files
This section provides instructions to create a custom monitor for monitoring all the open files for
JVMs.
1. Create a new directory in the custom monitor repository.
2. Create the script file.
This is a sample script. Modify this script for the specific process name (for example: Author,
Publish, and so on).
lookfor="<process name 1>"

pid=`ps aux | grep "$lookfor" | grep -v grep | tr -s " " | cut
-f2 -d' '`
count1=`lsof -p $pid | wc -l | xargs`
lookfor="<process name 2>"

pid=`ps aux | grep "$lookfor" | grep -v grep | tr -s " " | cut
-f2 -d' '`
count2=`lsof -p $pid | wc -l | xargs`
echo "name=JVM|Files|<process name 1>,value="$count1

echo "name=JVM|Files|<process name 2>,value="$count2
3. Create the monitor.xml and point this XML file to the script file created in step 2.
<monitor>
<name>MyMonitors</name>
<type>managed</type>
<description>Monitor open file count </description>
<monitor-configuration>
</monitor-configuration>
<monitor-run-task>
<execution-style>continuous</execution-style>
<name>Run</name>
<type>executable</type>
<task-arguments>
</task-arguments>
<executable-task>
<type>file</type>
<file>openfilecount.sh</file>
</executable-task>
</monitor-run-task>
</monitor>

On this page:
Before You Begin
Process for Creating a Monitoring Extension in Java
Your Monitoring Extension Class
The monitor.xml File
Using Your Monitoring Extension as a Task in a
Workflow
Related pages:
Watch the video:
Standalone Machine Agent - Overview of Custom Extensions -
1:06
Direct Link: https://player.vimeo.com/video/110812089
A Java monitoring extension enables the Standalone Machine Agent to collect custom metrics,
which you define and provide, and to report them to the Controller. This is an alternative to adding
monitoring extensions using scripts.
When you capture custom metrics with a monitoring extension, they are supported by the same
AppDynamics services that you get for the standard metrics captured with the AppDynamics
application and machine agents. These services include automatic baselining, anomaly detection,
display in the Metric Browser, availability for display on custom dashboards and availability for use
in policies to trigger alerts and other actions.
This topic describes the procedure for creating a monitoring extension in Java.
To the Standalone Machine Agent, a monitoring extension is a task that runs on a fixed schedule
and collects metrics. The task can be either AJavaTask, which executes a task within the machine
agent process, or AForkedJavaTask, which executes a task in its own separate process.
Before You Begin
Before creating your own extension from scratch, look at the extensions that have been created
and shared among members of the AppDynamics community. The extensions are described and
their source is available for free download at:
https://github.com/Appdynamics/
New extensions are constantly being added. It is possible that someone has already created
exactly what you need or something close enough that you can download it and use it after making
a few simple modifications.
Process for Creating a Monitoring Extension in Java

To create a monitoring extension in Java:
1. Create your extension class. See Your Monitoring Extension Class.
2. Create a monitor.xml configuration file. See The monitor.xml File.
3. Create a zip file containing these two files plus any dependent jar files.
4. Create a subdirectory (<your_extension_dir>) in <agent home>/monitors.
5. Unzip the zip file into <agent home>/monitors/<your_extension_dir>.
6. Restart the Standalone Machine Agent.
Your Monitoring Extension Class
Create a monitoring extension class by extending the AManagedMonitor class in the

com.singularity.ee.agent.systemagent.api package.
You will also need the following helper classes in the same package:
com.singularity.ee.agent.systemagent.api.MetricWriter:
com.singularity.ee.agent.systemagent.api.TaskExecutionContext;
com.singularity.ee.agent.systemagent.api.TaskOutput;
com.singularity.ee.agent.systemagent.api.exception.TaskExecutionException
The Javadoc for these APIs is available at:
https://rawgithub.com/Appdynamics/java-sdk/master/machine-agent-api/MachineAgentAPIJavado
cs/index.html
Your monitor extension class performs these tasks:
Populates a hash map with the values of the metrics that you want to add to AppDynamics.
How you obtain these metrics is specific to your environment and to the source from which
you derive your custom metrics.
Describes the metrics using the MetricWriter class.
Uploads the metrics to the Controller using the execute() method of the TaskOutput class.
Metric Path
All custom metrics processed by the Standalone Machine Agent appear in the Application
Infrastructure Performance tree in the metric hierarchy.
Within the Application Infrastructure Performance tree you specify the metric path, which is the
position of the metric in the metric hierarchy, using the "|" character. The first step in the metric
path must be "Custom Metrics."
For example:
Custom Metrics|WebServer|
Custom Metrics|WebServer|XXX|, CustomMetrics|WebServer|YYY|
If the metrics apply to a specific tier, use the metric path for the tier, with "Component" followed by
a colon ":" and the tier ID. The metric will appear under the specified tier in the metric path. For
example:
Server|Component:18|

Server|Component:18|CustomMetric|Path|
To discover the component ID of a tier, select the tier from the Controller UI application tree. The
component ID appears in the URL of the browser.
You can insert a custom metric alongside an existing type of metric. For example, the following
declaration causes the custom metric named pool usage to appear alongside the JMX metrics:
name=Server|Component:18|JMX|Pool|First|pool usage,value="$pool_value
The metric can then be used in health rules as would other types of JMX metrics.
You can test the appearance of your custom metric in the Controller API by posting the
metric data to the machine agent's REST API. Pass the path, name type and values of the
metric as URL arguments. See Standalone Machine Agent HTTP Listener for more
information.
Metric Names
Metric names must be unique within the same metric path but need not be unique for the entire
metric hierarchy.
It is a good idea to use short metric names so that they will be visible when they are displayed in
the Metric Browser.
Prepend the metric path to the metric name when you upload the metrics to the Controller.
Metric Processing Qualifier
The Controller has various qualifiers for how it processes a metric with regard to aggregation, time
rollup and tier rollup.
There are three types of metric qualifiers:
Aggregation qualifier
Time roll-up qualifier
Cluster roll-up qualifier
You specify these options with the enumerated types provided by the MetricWriter class. These
types are defined below.

Aggregation Qualifier
The aggregator qualifier specifies how the Standalone Machine Agent aggregates the values
reported during a one-minute period.
Specify the aggregation qualifier as aggregator="aggregator type"
This value is an enumerated type. Valid values are:
Aggregator Type Description
METRIC_AGGREGATION_TYPE_AVERAGE Default. Average of all reported values in

that minute.
METRIC_AGGREGATION_TYPE_SUM Sum of all reported values in that minute,

causes the metric to behave like a
counter.
METRIC_AGGREGATION_TYPE_OBSERVATION Last reported value in the minute. If no

value is reported in that minute, the last
reported value is used.
Time Roll Up
The time-rollup qualifier specifies how the Controller rolls up the values when it converts from
one-minute granularity tables to 10-minute granularity and 60-minute granularity tables over time.
Roll up Strategy Description
METRIC_TIME_ROLLUP_TYPE_AVERAGE Average of all one-minute data points when

adding it to the 10-minute or 60-minute
granularity table.
METRIC_TIME_ROLLUP_TYPE_SUM Sum of all one-minute data points when adding

it to the 10-minute or 60-minute granularity table.
METRIC_TIME_ROLLUP_TYPE_CURRENT Last reported one-minute data point in that

10-minute or 60-minute interval.
Cluster Roll Up
The cluster-rollup qualifier specifies how the controller aggregates metric values in a tier.
Roll up Strategy Description
METRIC_CLUSTER_ROLLUP_TYPE_INDIVIDUAL Aggregates the metric value by

averaging the metric values across each
node in the tier.
METRIC_CLUSTER_ROLLUP_TYPE_COLLECTIVE Aggregates the metric value by adding

up the metric values for all the nodes in
the tier.

For example, if a tier has two nodes, Node A and Node B, and Node A has 3 errors per minute
and Node B has 7 errors per minute, the INDIVIDUAL qualifier reports a value of 5 errors per
minute and COLLECTIVE qualifier reports 10 errors per minute. INDIVIDUAL is appropriate for
metrics such as % CPU Busy where you want the value for each node. COLLECTIVE is
appropriate for metrics such as Number of Calls where you want a value for the entire tier.
Sample Monitoring Extension Class
The NGinXMonitor class gets the following metrics from the Nginx Web Server and adds them to
the metrics reported by AppDynamics:
Active Connections: number of active connections
Accepts: number of accepted requests
Handled: number of handled requests
Requests: total number of requests
Reading: number of reads
Writing: number of writes
Waiting: number of keep-alive connections
The source for the extension class is included as an attachment.
The monitor.xml File
Create a monitor.xml file with a <monitor> element to configure how the machine agent will
execute the extension.
1. Set the <name> to the name of your Java monitoring extension class.
2. Set the <type> to "managed".
3. The <execution-style> can be "continuous" or "periodic".
Continuous means to collect the metrics averaged over time; for example, average
CPU usage per minute. In continuous execution, the Standalone Machine Agent
invokes the extension once and the program runs continuously, returning data every
60 seconds.
Periodic means to invoke the monitor at a specified frequency. In periodic execution
the Standalone Machine Agent invokes the extension, runs it briefly, and returns the
data on the schedule set by the <execution-frequency-in-seconds> element.
4. If you chose "periodic" for the execution style, set the frequency of collection in
<execution-timeout-in-secs> element. The default frequency is 60 seconds. If you chose
"continuous" this setting is ignored.
5. Set the <type> in the <monitor-run-task> child element to "java".
6. Set the <execution-timeout-in-secs> to the number of seconds before the extension times
out.
7. Specify any required task arguments in the <task-arguments> element. The default
arguments that are specified here are the only arguments that the extension uses. They are
not set anywhere else.
8. Set the <classpath> to the jar file that contains your extension's classes. Include any
dependent jar files, separated by semicolons.
9.

9. Set the <impl-class> to the full path of the class that the Standalone Machine Agent invokes.
Sample monitor.xml Files
This attached monitor.xml file configures the NGinXMonitor monitoring extension. This extension
executes every 60 seconds.
This attached monitor.xml file configures the MysqlMonitor. This monitor executes every 60
seconds, has four required task arguments and one optional task argument and one dependent jar
file.
Using Your Monitoring Extension as a Task in a Workflow
Your monitoring extension can be invoked as a task in a workflow if you upload the zip file to the
task library. Use the instructions in To package the XML files as a Zip archive to upload the Java
monitor to the Task Library.

On this page:
Activate the HTTP listener
Send metrics
Send events
Upload metrics
Upload events
Shut down the Standalone Machine Agent
You can send metrics to the Standalone Machine Agent using its HTTP listener. You can report
metrics through the Standalone Machine Agent by making HTTP calls to the agent instead of
piping to the agent through sysout.
Activate the HTTP listener
Restart the Standalone Machine Agent using metric.http.listener:
java -Dmetric.http.listener=true -Dmetric.http.listener.port=<port_number>

-jar machineagent.jar
If you do not specify the optional metric.http.listener.port, it defaults to 8293.
Send metrics
GET | POST /machineagent/metrics
Send events

GET /machineagent/event
Upload metrics
You can use GET or POST to upload metrics to the Metric Browser under Application
Performance -> <Tier> where the tier is the one defined for the Standalone Machine Agent. For
example:
http://host:port/machineagent/metrics?name=Custom Metrics|Test|My
Metric&value=42&type=average
Valid values for type are:

average
sum
current
Upload events
Send events using HTTP get requests to:
http://localhost:8293/machineagent/event?type=<event_type>&summary=<summary_text
>
Event_type is one of the following:

error
info
summary
warning
Shut down the Standalone Machine Agent
GET /machineagent/shutdown
JVM Crash Guard
On this page:
To Start Monitoring for JVM Crashes
Related pages:
Server Monitoring

Watch the video:
Standalone Machine Agent - Overview of JVM Crash

Guard
When a JVM crash occurs,you need to be notified as soon as possible. Learning of a JVM crash
is very critical because it maybe a sign of a severe runtime problem in an application.
Furthermore, you may want to to take remediation steps once you are aware that a crash event
has occurred. JVM Crash is a new event type, implemented as part of JVM Crash Guard, that you
can activate to provide you with the critical information you need to expeditiously handle JVM
crashes.
The following image shows the Events window where notification of two JVM Crash events
detected is displayed.
Double-clicking the JVM Crash event on the Events window displays more information to assist
you in troubleshooting the underlying reason for the JVM crash.
On the Summary page you can download any logs associated with the JVM Crash event.

The JVM Crash window also displays information about actions executed as a result of the crash.
These are actions that you specify when creating the policy that is triggered by a JVM crash event.
The JVM Crash event captures the following information: timestamp, crash reason, host name, IP

address, process ID, application name, node name, and tier name and displays them on the
details page.
In the Crash Reason details field of the JVM Crash Details tab, the JVM Crash details indicate the
root cause of the crash if available; for example, a java.lang.OutOfMemoryError, Segmentation
Fault, etc... To facilitate the discovery and display of the reason for the JVM crash, JVM Crash
Guard provides full support for:
Hotspot JVM error log analysis
IBM JVM System Dump log analysis
Jrockit JVM error log analysis
To Start Monitoring for JVM Crashes
Prerequisite
JVM Crash Guard is a policy trigger that works with the Standalone Machine Agent to fire
an AppDynamics policy when a JVM Crash event occurs. You must therefore have a
Standalone Machine Agent installed on the system which you want to monitor for JVM
crashes. On Windows, the Standalone Machine Agent must run in Administrator root
mode. On Linux, JVM Crash Guard requires that the Standalone Machine Agent user be
able to read all the processes in /proc/*. This may be the ‘root’ user or another user with
this privilege.
1. From the left-hand navigation menu, click Alert & Respond ->Policies and then click Creat
e a Policy.
OR
Navigate to the Policies tab and then click Create a Policy.
The Create Policy dialog appears.
2. In the Other Events section, expand the Server Crashes option and click JVM Crash.
The JVM Crash event then becomes a trigger to fire a policy.
3.

3. Proceed as usual to create the Policy. For more information on creating Policies, see Policie
s.
Note: If an uninstrumented JVM crash happens within less than a minute of a previous crash then
it will not be reported by the Standalone Machine Agent. In some circumstances, the JVM may
crash and then be restarted only to crash again within one minute. For this repetitive cycle crash
and restart scenario, only the first JVM crash is reported by the agent.
Remediation Scripts
On this page:
Prerequisites for Local Script Actions
Remediation Scripts
Troubleshooting Remediation Scripts
Related pages:
Actions
Policies
Remediation Actions
Extensions and Integrations

Watch the video:
Standalone Machine Agent - Overview of Running
Remediation Scripts
A remediation action runs a remediation script in a node. The script executes on the machine from
which it was invoked or on the node specified by the remediation action configuration. You can use
this type of action to automate your runbook procedures. For example, when a specific event
occurs such as a JVM crash or a code problem and triggers a policy that calls the script, you could
have the remediation script restart the JVM or increase the size of the connection pool on the JVM
respectively.
Prerequisites for Local Script Actions

The Standalone Machine Agent must be installed running on the host on which the script
executes. To see a list of installed machine agents for your application, click View
machines with machine-agent installed in the bottom left corner of the remediation script
configuration window.
To be able to run remediation scripts, the machine agent must be connected to an
on-premise Controller or to a SaaS Controller via SSL. Remediation script execution is
disabled if the machine agent connects to a SaaS Controller on an unsecured (i.e.,
non-SSL) HTTP connection.
The Standalone Machine Agent OS user must have full permissions to the script file and the
log files generated by the script and/or its associated child processes.
The script must be placed in <agent install directory>\local-scripts.
The script must be available on the host on which it executes.
Processes spawned from the scripts must be daemon processes
Remediation Scripts
A remediation script is run on the machines that you specify in the remediation script configuration.
You can run the script from the machine affected by the violation that triggered the action or from a
central management server. It is not necessary for an app agent to be running on the machine on
which the script executes, just a Standalone Machine Agent.
Guidelines for Remediation Scripts
By default the script is a shell script in /bin/sh invoked with the -ex option, unless the script has a
header, in which case the interpreter in the header is used. For example, if the script header is
"#!/bin/perl", the PERL interpreter is invoked.
A process exit code of zero indicates that the script execution succeeded. A non-zero exit code
indicates that it failed.
The script should be written as generically as possible to allow it run on any of the nodes for which
is it invoked. AppDynamics exports the following environment variables to the script runtime to
provide context regarding the environment and the event that triggered the action.

Environment Variable Cardinality Notes
(1 or N)
APP_ID 1 Name of the Application
EVENT_TIME 1 Timestamp of the event
EVENT_ID 1 Event Id
EVENT_TYPE 1 type of event, such as: ERROR,

APPLICATION_ERROR, APPLICATION_INFO,
STALL, BT_SLA_VIOLATION, DEADLOCK,
MEMORY_LEAK,
MEMORY_LEAK_DIAGNOSTICS,
LOW_HEAP_MEMORY, ALERT, CUSTOM,
APP_SERVER_RESTART, BT_SLOW,
SYSTEM_LOG,
INFO_INSTRUMENTATION_VISIBILITY,
AGENT_EVENT, INFO_BT_SNAPSHOT,
AGENT_STATUS, SERIES_SLOW,
SERIES_ERROR, ACTIVITY_TRACE,
OBJECT_CONTENT_SUMMARY,
DIAGNOSTIC_SESSION,
HIGH_END_TO_END_LATENCY,
APPLICATION_CONFIG_CHANGE,
APPLICATION_DEPLOYMENT,
AGENT_DIAGNOSTICS, MEMORY, LICENSE
ENV_STARTUP_ARGS 1 Process args
ENV_SYSTEM_PROPERTIES 1 JVM System Props (When Java)
AFFECTED_ENTITY 1 Affected Entity that triggered the event
Remediation scripts must be stored in a sub-directory of the machine agent installation. The
sub-directory must be named "local-scripts". The following paths are all valid:
${machine.agent.home}/local-scripts/runMe.sh
${machine.agent.home}/local-scripts/johns_scripts/runMe.sh
${machine.agent.home}/local-scripts/ops/johns_scripts/runMe.sh
Troubleshooting Remediation Scripts

To troubleshoot your remediation script, look for the process in the machine agent log. The log is
located at

<machine agent home>/logs/machine-agent.log
The snippet below from the machine agent log shows both error and success messages from
running a local script named "script.sh".
Administer the Standalone Machine Agent

Related pages:
Server Monitoring
Standalone Machine Agent Requirements and
Supported Environments
The AppDynamics Pro Controller and agents are easy to install and administer.
The following topics describe procedures and provide reference material relevant to the
AppDynamics Pro Administrator.
Upgrade the Standalone Machine Agent
Determine Whether a Server is Down
Controller Settings for Machine and Database Agents
Machine Agent FAQ
Upgrade the Standalone Machine Agent
Related pages:
Agent - Controller Compatibility Matrix

Note: If you are upgrading both the Controller and agents, first upgrade the Controller and then
upgrade the agents. When upgrading multiple agents, upgrade the agents for the tiers on which
business transactions originate last.
1. Download the latest version of the Standalone Machine Agent from the AppDynamics
Download Center.
2. Stop the Standalone Machine Agent process.
3. Backup the current agent installation directory and rename it.
4. Extract the Standalone Machine Agent archive to a new directory.
5. Rename the new directory to the original name of the agent directory in order to avoid
manually changing agent-related configurations.
6. Modify the <agent install directory>/controller-info.xml as appropriate.
7. Restart the agent.
8. Archive the previous agent directory and remove it from the application server.
Determine Whether a Server is Down

On this page:
Discovering the Status of a Server
Related pages:
App Servers List
Metric Browser
Discovering the Status of a Server
If an application server agent is not reporting to the Controller, the App Agent Status in the App
Servers list displays a red icon with a downward-facing arrow and a status of zero.
Similarly, if a machine agent is not reporting to the Controller, the Machine Agent Status in the App
Servers list displays the same icon.
If the agent is not reporting, it is possible that the server is down, although here could be other
reasons why the agent is not reporting.
To investigate further, in the Metric Browser locate the individual node in question in the Agent
branch of the Application Infrastructure Performance tree. If the value of the Availability metric for
the application is zero, the app server is down. If the value of the Availability metric for the
machine is zero, the machine is down.

Controller Settings for Machine and Database Agents
On this page:
Related pages:
Access the Administration Console
Database Size and Data Retention
The following describes settings on the Controller Admin window that are specific to the Database
Agent and Standalone Machine Agent.
You can change the amount of data you retain in the Controller database by changing the

retention period for machine agent and database agent snapshots. Lowering the retention settings
purges data that is aged out by the new retention setting and reduces the amount of data stored
by the Controller on an ongoing basis. When tuning the size of the MySQL database
AppDynamics uses, this is a good place to start.
To change the Controller Settings for Standalone Machine Agents and Database Agents
1. Log in to the Controller administration console using the root account password. See Acces
s the Administration Console.
http://<controller host>:<port>/controller/admin.html
Use the root account password to access the Admin console when the Controller is installed
in single- or multi-tenant mode. If you have not set this password, call AppDynamics Support
to get the default password.
2. Click Controller Settings.
3. Change the following parameters as required and then click Save.
Property Name About the property Default Allowed

Values
machine.agent.in-progress.actions.timeout Determines how long the 86400000 1 to 840

Controller waits for the msec hours (5
agent to perform an weeks)
IN-PROGRESS action
before it stops the action.
machine.agent.max.new.actions.per.min Maximum number of new 15 1 to

actions dispatched per 28999999
minute for each machine
agent. This is the
maximum number of
"runbook" actions sent to
the machine agent. For
example, you may request
the machine agent to run a
script because of a health
rule violation, if the number
is more than the preset, it
will be sent the next
minute. Default 15
machine.agent.pending.actions.timeout Determines how long the 1800000

Controller waits for the msec
agent to perform a
PENDING action before it
stops the action.

machine.agent.snapshots.buffer.size Determines the buffer size 50 MB
used for server snapshots
collected by the machine
or database agent.
machine.snapshots.retention.period Determines the retention 336 hours 1 to 840

time for server snapshot (2 weeks) hours (5
data in hours. weeks)
app.agent.max.new.actions.per.min Maximum number of new

actions dispatched per
minute for each agent.
Actions sent to the app
agent, as opposed to the
machine or database
agent, include thread
dumps.
Changes to the settings will be in effect the next time the agent is restarted and connects to the
Controller.
Machine Agent FAQ

On this page:
Shut Down the Standalone Machine Agent
Identify the Standalone Machine Agent Process
Reset a Standalone Machine Agent
Determine if a Server is Down
Metric Values for Disk and Network are Zero
Flow Maps and the Standalone Machine Agent
Server Health Indicator and the Standalone Machine
Agent
Resolve Metric Reporter Type Mismatch Problem
Shut Down the Standalone Machine Agent
If the machine agent process is running in the background, you can stop it by simply entering the
kill command with the process ID as the argument. If it is running in the foreground in a console,
you can press Ctrl+C to shut down the agent.
Note that the Machine Agent implements a shutdown hook, so issuing the kill command (or Ctrl+C)
from the operating system causes the the agent to perform a graceful shut down.
Identify the Standalone Machine Agent Process
For Linux
Use the following command to identify which process is running the Standalone Machine Agent.

ps -ef | grep machine
For Windows
Process Explorer is a free application from Microsoft that can help you identify the Standalone
Machine Agent process. When there are multiple java processes running, hover over a java
process in Process Explorer to identify the process that was started using the machineagent.jar
file.
For example, in Process Explorer, hover over a process to see information about how the process
was started as you can see in the following window:
Reset a Standalone Machine Agent
1. Navigate to the Settings > AppDynamics Agents window in the Controller.

2. On the AppServer and Machine Agents tab, select an agent in the Machine Agents pane.
3. Click Reset Selected Machine Agent.
The reset operation purges all existing metrics for an agent and starts gathering them again. It
stops the agent and starts it again.
Determine if a Server is Down
If an application server agent is not reporting to the Controller, the App Agent Status in the App
Servers list displays a red icon with a downward-facing arrow and a status of zero.
Similarly, if a machine agent is not reporting to the Controller, the Machine Agent Status in the App

Servers list displays the same icon.
If the agent is not reporting, it is possible that the server is down, although here could be other
reasons why the agent is not reporting.
To investigate further, in the Metric Browser locate the individual node in question in the Agent
branch of the Application Infrastructure Performance tree. If the value of the Availability metric for
the application is zero, the app server is down. If the value of the Availability metric for the
machine is zero, the machine is down.
Metric Values for Disk and Network are Zero
This situation may occur when a 32-bit JRE is used with 64-bit operating system. To solve this
problem, use a 64-bit JRE with the 64-bit operating system.
Flow Maps and the Standalone Machine Agent
The Standalone Machine Agent monitors a particular machine and not a particular application
server. The agent can therefore refer to multiple nodes running on the same machine. A flow map,
on the other hand, displays the communication between different nodes during application
execution, or the business transaction flow from tier to tier. A Standalone Machine Agent cannot
be a part of the flow and therefore is not shown in the flow map.
Server Health Indicator and the Standalone Machine Agent
Metrics monitored by the agent are included in the infrastructure health indicator in the
dashboards.
The health indicator is driven by health rule violations in the given time period and health rule
violations are configured on hardware metrics collected by the Standalone Machine Agent. Health
rules for all possible metrics are not pre configured out-of-the-box. To configure additional health
rules, see Configure Health Rules.
Resolve Metric Reporter Type Mismatch Problem
Switch from the Java Hardware Monitor to the Hardware Monitor if you see messages similar to
the following in the logs:
[Worker-7] 12 Sep 2014 07:27:49,449 WARN MonitorOutputHandler - Metric Reporter

type mismatch for metric [Hardware Resources|Network|Incoming packets/sec]
com.singularity.ee.agent.commonservices.metricgeneration.metrics.MetricReporterT
ypeMismatchException: Aggregator of OBSERVATION already exists for metric Metric
Identifier[Hardware Resources|Network|Incoming packets/sec] ID[0]

PRO40 Server Monitoring 01july2015

Uploaded by

Copyright:

Available Formats

PRO40 Server Monitoring 01july2015

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PRO40 Server Monitoring 01july2015

Uploaded by

Copyright:

Available Formats

Server Monitoring

AppDynamics Pro Documentation

Standalone Machine Agent Requirements and Supported

Supported Platform Matrix for the Standalone Machine Agent

JVM Requirements for the Standalone Machine Agent

Copyright © AppDynamics 2012-2015 Page 3

Supported Platforms for Default Hardware Monitor Plugin

Operating Architecture Versions

Linux x86 2.2, 2.4, 2.6 kernels

Linux amd64 2.6 kernel

Linux ppc 2.6 kernel

Linux ppc64 2.6 kernel

Linux ia64 2.6 kernel

Linux s390 2.6 kernel

Linux s390x 2.6 kernel

Solaris Sparc-32 2.6, 7, 8, 9, 10

Solaris Sparc-64 2.6, 7, 8, 9, 10

AIX ppc 4.3, 5.1, 5.2, 5.3, 6.1

AIX ppc64 5.2,5.3,6.1

FreeBSD x86 4.x

FreeBSD x86 5.x, 6.x

FreeBSD x64 6.x

FreeBSD x86,x64 7.x,8.x

OpenBSD x86 4.x,5.x

NetBSD x86 3.1

Mac OS X PowerPC 10.3, 10.4

Copyright © AppDynamics 2012-2015 Page 4

Mac OS X x64 10.5, 10.6

Windows x64 2003 Server, Vista, 2008 Server, 7

The following Linux distributions have been certified:

Red Hat 6.2, 7.3, 8.0, 9.0

Ubuntu 6.06, 8.04, 8.10, 9.04

Debian 2.6, 3.0, 3.1, 3.2, 4.0, 5.0

VMware ESX 2.x, 3.0

XenServer 3.1, 3.2, 4.0, 4.1, 5.0

Copyright © AppDynamics 2012-2015 Page 5

Standalone Machine Agent Architecture

Copyright © AppDynamics 2012-2015 Page 6

Getting Started with the Standalone Machine Agent

1. Confirm you have access to an AppDynamics Controller:

Copyright © AppDynamics 2012-2015 Page 7

8. You're ready to begin monitoring.

Install the Standalone Machine Agent

Configure using controller-info.xml: <controller-host>

Copyright © AppDynamics 2012-2015 Page 8

Configure using controller-info.xml: <account-name>

Configure using controller-info.xml: <account-access-key>

7. Configure the business application, tier, and node.

Configure using controller-info.xml: <application-name>

Configure using controller-info.xml: <tier-name>

Configure using controller-info.xml: <node-name>

Copyright © AppDynamics 2012-2015 Page 9

java -Xmx32m -jar machineagent.jar

nohup java -Xmx32m -jar machineagent.jar &

java -Xms64m -Xmx64m -jar machineagent.jar &

10. Verify the agent installation.

Started AppDynamics Machine Agent Successfully

This message is also printed on the STDOUT of the process.

Standalone Machine Agent Configuration Properties