PDFs


This page applies to an earlier version of the AppDynamics App IQ Platform.
For documentation on the latest version, see the 4.4 Documentation.


On this page:

Related pages:

Your Rating:
Results:
PatheticBadOKGoodOutstanding!
44 rates

The Standalone Machine Agent (Machine Agent) collects and displays CPU, Memory, Disk, and Network metrics on the Node Dashboard Server tab. You can view additional metrics in the Metric Browser > Application Infrastructure Performance  > Hardware Resources.

You can use the hardware metrics on Custom Dashboards. 

To add CPU metrics to your Custom Dashboard, add the metrics for any node on your target machine. Metrics collected for a node associated with the machine agent are for server hosting that node. Any machine metrics collected will be the same for nodes that are on the same machine.

Customize Default Metrics

Enable collection of metrics for virtual disks and external network traffic.

Add Custom Metrics

You can add script-based and Java-based custom monitoring extensions to collect additional metrics. For example, the ehCache monitoring extension available from AppDynamics Exchange can collect metrics to monitor Ehcache performance. The metrics appear in Application Infrastructure Performance | Custom Metrics section of the Metric Browser and can be used on custom dashboards.

You can also send metrics to the Machine Agent using the HTTP listener 

For a more complete discussion of adding custom metrics, see Extensions and Custom Metrics.

Hardware Metric Reference

This section describes the basic hardware metrics collected by the Machine Agent. Not all of the metrics that appear in the Hardware Resources branch of the Metric Browser tree are provided by the Machine Agent; some are collected by the Database Agent and are used in the Database Monitoring UI, while others may be custom metrics added by another extension run by your Standalone Machine Agent. 

For most metrics in the browser, you can click any of the points in the graph to view more information about the metric observed at that point in time. The information includes the metric identifier, date and time of the observation, along with any of the following values relevant to the metric:

  • Obs (observed value): the average of all data points seen for that interval. For a cluster or a time rollup, this represents the weighted average across nodes or over time. 
  • Min: the minimum data point value seen for that interval
  • Max: the maximum data point value seen for that interval
  • Sum: the sum of all data point values seen for that interval. For the Percentile Metric for the App Agent for Java, this is the result of the percentile value multiplied by the Count.
  • CountMachine agent metric observation varies depending on the OS. 
    • For AIX, HP-UX, Mac OS X and Z/OS, the count depends on the metric: 
      • For disk and network metrics: One observation per minute. When you view the count for these metrics in the Metric Browser you see the count of 1 per minute. If you select a 15-minute interval, the count would be 15 times 1 = 15 and so on.
      • For CPU and memory metrics: One observation every two seconds.  When you view the count for these metrics you see the count of 30 per minute. If you select a 15-minute interval, the count would be 15 times 30 = 450 and so on.
    • For Windows, Linux: agent takes one observation every 30 seconds, so the count is two per minute.
    • For an explanation of how the count is rolled up to the tier, see the section Metric Processing Qualifier here: Build a Monitoring Extension Using Java.

Hardware Metrics Provided by Standalone Machine Agent

CPU Metrics

%Busy: The percentage of time the CPU was busy processing system or user requests plus CPU Stolen.

%Idle: The percentage of time the CPU was idle; the CPU had completed its tasks and has nothing to do.

%Stolen: Usually stolen time is the percentage of time a virtual CPU waits for a real CPU while the hypervisor is servicing another virtual processor. Note: CPU % Stolen is not available for Windows Servers.

 

Disk and Partition Metrics

 

KB read/sec: The average rate of data read per second (all disks and partitions).

KB written/secThe average rate of data written per second (all disks and partitions).

Reads/sec: Number of read operations per second (all disks and partitions).

Writes/sec: Number of write operations per second (all disks and partitions).

<partition>, %CPU Time: The percentage of CPU processing consumed by a partition during read and write operations. Note: this metric is not available for Windows servers.

<partition>, Avg Service Time (ms): Time in milliseconds spent performing read and write operations across one partition. Note: this metric is not available for Windows servers.

<partition>, Avg Queue Time (ms): Time in milliseconds that a read or write request is in the queue before it gets processed across one partition. Note: this metric is not available for Windows servers.

<partition>, KB read/sec: The average amount of data per second read from one specific partition.

<partition>, KB written/sec: The average amount of data per second written to one specific partition. 

<partition>, Reads/sec: Number of read operations per second performed on one specific partition.

<partition>, Writes/sec: Number of write operations per second performed on one specific partition.

<partition>, Space Available: The amount of unused or free disk space on a specific partition in KB. 1

<partition>, Space Used: The amount of used or unavailable disk space on a specific partition in KB.1

 

Memory Metrics

Free %: Percentage of free or unused memory available for processes.

Free (MB): The total amount of free or unused memory available for processes.

Total (MB): The total amount of memory.

Used %: The percentage of memory used.

Used (MB): The amount of memory used.

Network Metrics

Incoming KB: The volume of data received by all monitored network devices.

Incoming KB/sec: The amount of data per second received by all monitored network devices.

Incoming packets: The number of data packets per second received by all monitored network devices.

Incoming packets/sec: The number of data packets per second received by all monitored network devices.

Outgoing KB: The volume of data sent by all monitored network devices.

Outgoing KB/sec: The volume of data sent per second by all monitored network devices.

 Outgoing packets: The number of packets sent by all monitored network devices

Outgoing packets/sec: The number of data packets sent per second by all monitored network devices.

<network interface> Incoming KB: The volume of data received by the selected network device.

<network interface> Incoming KB/sec: The volume of data received per second by the selected network device.

<network interface> Incoming packets: The number of data packets received by the selected network device.

<network interface> Incoming packets/sec: The number of data packets received per second by the selected network device.

<network interface> Outgoing KB: The volume of data sent by the selected network device.

<network interface> Outgoing KB/sec: The volume of data sent per second by all monitored network devices.

<network interface> Outgoing packets: The number of data packets sent per second by the selected network device.

<network interface> Outgoing packets/sec: The number of data packets sent per second by the selected network device.

 

1  Linux includes a mechanism for reserving some disk space to ensure that the system keeps functioning even if non-privileged users consume all other disk space. The Space Available and Space Used metrics on Linux do not include this reserved space. Therefore, the total disk space reported by the agent (Space Available + Space Used) might differ from the total disk space reported by the Linux df command or other sources. For more information, see the Linux man page for the tune2fs command.

Watch the Video

For full-screen viewing, click Standalone Machine Agent: Overview of Metrics Collected.