Skip to end of metadata
Go to start of metadata

Why is the Machine Agent not displayed on the Flow Map?

The Machine Agent monitors a particular machine and not a particular application server or JVM. The Machine 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 Machine Agent cannot be a part of the flow and therefore is not shown in the Flow Map.

Are the metrics monitored by the Machine Agent included in the Infrastructure Health indicator in the Main Dashboard?

Yes, 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 Machine Agent. Health Rules for all possible metrics are not configured out-of-the-box, so you might want to configure additional health rule according to your requirements. For details see Configure Health Rules.

How can I configure the Machine Agent to run automatically when the machine starts?

To enable the machine agent to run as a Linux (or Windows) service, use the instructions listed below:

Instructions for Linux environments

1. Create a script file as shown below:

#!/bin/sh
# -----------------------------------------------------------------------------
# Typical AppDynamics Machine Agent Startup
# -----------------------------------------------------------------------------

#CHANGE ME: Set to the agent's install directory
JAVA=java

#CHANGE ME: Set to the agent's install directory
AGENT_HOME=/opt/appdynamics/machineagent
AGENT="$AGENT_HOME/machineagent.jar"

# Agent Options
# Uncomment and make available as needed
# -Dappdynamics.agent.applicationName   : application that the agent participates in
# -Dappdynamics.agent.logging.dir       : directory to put logs (agent "user" must have write permissions
# -Dmetric.http.listener=true | false   : open a kill port
# -Dmetric.http.listener.port			: the port to send kill messages

AGENT_OPTIONS=
#AGENT_OPTIONS="$AGENT_OPTIONS -Dappdynamics.agent.applicationName=<application-name>"
#AGENT_OPTIONS="$AGENT_OPTIONS -Dappdynamics.agent.logging.dir="
#AGENT_OPTIONS="$AGENT_OPTIONS -Dmetric.http.listener=true | false
#AGENT_OPTIONS="$AGENT_OPTIONS -Dmetric.http.listener.port=<port>"

#Consolidation Step - allows you to easily add or remove the agent
#Call the nohup $JAVA $AGENT_OPTIONS -jar $AGENT &

2. Add the script to the rc script.

For Red Hat and most Linux Operating Systems

For Ubuntu and Debian Operating Systems

Add the script file created in Step-1 in /etc/rc.local
For example:
echo '/path/to/startup/script.sh start' >> /etc/rc.local

Add the script file created in Step-1 as shown below:
For example:
update-rc.d -f script.sh start 99 2 3 4 5.
where

  • 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
    (warning) IMPORTANT: Do not forget to add dot(.) at the end.

Instructions for Microsoft Windows environments

See Configure the Machine Agent to Automatically Start on Windows.

How do I shut down the 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.

If the machine is hosting servers that belong to multiple business applications, how do I assign the Machine Agent to multiple applications?

You can configure the Machine Agent with its own Application/Tier/Node properties. If there are Nodes belonging to multiple business applications, you can run multiple Machine Agents each configured to report metrics for a different Node, Tier, and Application. For details see Install the Standalone Machine Agent.

Background information: You cannot "assign" a Machine Agent to multiple business application per se. A 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 Machine Agents of its Nodes. By default Machine Agents inherit the Application/Tier/Node names of the App Agents installed on the same hardware.

Why are all the metrics for disk reads and writes and/or network I/O statistics 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.

Learn More