This topic describes the additional metrics collected by the Standalone Machine Agent for Server Monitoring. Server Monitoring is currently available for Linux and Windows. The metrics can be viewed from the Servers tab of the AppDynamics Controller and from the Metric Browser.
Server Monitoring metrics can only be viewed in the Server Monitoring version of the Metric Browser. You see this when you access the Metric Browser from the Servers tab in the top navigation bar of the Controller.
For most types of 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 shown 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.
- Count: the number of data points generated for the metric in that interval. This is information can be useful because the collection interval for infrastructure metrics varies by environment.
This reference describes metrics that are available only with Server Monitoring. The metrics are reported for both Windows and Linux servers unless otherwise noted. The basic hardware metrics are described in Machine Agent Hardware Metrics.
Some metrics that appear in the Hardware Resources branch of the Metric Browser are collected by the Database Agent and are used in the Database Monitoring UI, while others may be custom metrics added by extensions run by your Machine Agent.
Note: These CPU metrics are not available for Windows Servers
%Nice: % CPU time spent on low priority processes.
%Irq: % CPU time spent servicing/handling hardware interrupts.
%SoftIrq: % CPU time spent servicing/handling software interrupts
System: The percentage of time the CPU was busy processing kernel code.
User: The percentage of time the CPU was busy processing non-kernel code.
IOWait: The percentage of time the CPU spent waiting for an I/O request.
The disk metrics are reported for each disk partition and for all disks.
Avg IO Utilization (%): The average time spent processing read/write requests as a percentage of the total reported time window. Databases often report high disk I/O utilization due to frequent read/write requests. For example, if the agent detects read/write processing in 55 out of 60 seconds, the Avg IO Utilization for that minute is 92%. This metric does not measure the amount of available disk space or read/write request sizes.
Avg read time (ms): The average time required to service a read request.
Avg write time (ms): The average time required to service a write request.
For some versions of Windows Server 2008 and Windows Vista, the Hardware Resources|Disks|<partition>|Avg Read Time (ms) and Hardware Resources|Disks|<partition>|Avg Write Time (ms) metrics will be reported as 0. This is due to a known bug with Windows, and can be resolved by downloading the hotfix: https://support.microsoft.com/en-us/kb/961435
The load metrics are reported for each machine.
The CPU % (reported as part of the basic Machine Agent metrics) is the percentage of the CPU consumed by processes that are currently running. Load takes into account processes that are waiting to run.
Last 1 minute: CPU Load, presented as an average.
Last 5 minutes: CPU Load, presented as an average over the last 5 minutes.
Last 15 minutes: CPU Load, presented as an average over the last 15 minutes.
Availability: The percentage of time the Machine Agent was reporting to the Controller. In the Server Monitoring UI, this provides a percentage with 6 digits of precision (i.e. 100.0000), in other words measuring up to 6 9's of availability. The Standalone Machine Agent sends a heartbeat to the AppDynamics Controller once per minute to indicate the agent is reporting.
Reported for each machine.
Reported for each hierarchical group.
Swap Free (MB): The total amount of free swap space.
Swap Total (MB): The total amount of allocated swap space.
Swap Used (MB): The amount of swap space used.
Swap Used %: The percentage of used swap space.
Swap Free %: Percentage of free swap space.
Avg Utilization (%): The average network utilization as a percentage of the maximum possible throughput. This metric is not reported if the agent cannot determine the throughput (not supported for some devices and Linux versions). The percentage is rounded to the nearest integer. Therefore, very low utilizations might be reported as 0%. Reported for:
- <network device>
Incoming Errors/min: the rate of incoming packet errors the network incurs every minute. Not available for Linux Servers.
Outgoing Errors/min: the rate of outgoing packet errors the network incurs every minute. Not available for Linux Servers.
Process metrics are aggregated and reported per process. The Servers Process window displays the Top 10 Processes Consuming CPU and Top 10 Processes Consuming Memory. To modify the default process monitoring, see Configure Server Monitoring.
Count: The total number of processes in this class.
CPU Used (%): Percentage of the CPU bandwidth used by all processes in a process class. A process using 100% CPU is executing on all processors on the system.
Major Faults/sec: Number of major page faults caused by all processes in this class.
Minor Faults/sec: Number of minor page faults caused by all processes in this class.
Memory Used (%): Percentage of memory consumed by the top 10 consuming processes or the percentage of memory used by all processes in this class.
Memory Used (KB): Amount of memory used by all processes in this class.
Memory Virtual (KB): Current size of the virtual address space that the process is using. Use of virtual address space does not necessarily imply a corresponding use of either disk or main memory pages. Virtual space is finite and, by using too much, the process can limit its ability to load libraries.
Threads Count: The number of kernel threads used by all processes in this class.
Service Availability metrics are reported for each service that is configured.
Response Time (ms): The elapsed time between sending a request and receiving a response from the monitored service.
Response Size (bytes): The size of the response received from the monitored service.
Success Rate (%): The percentage of successful requests over all requests made to the service.
The volume metrics are reported across all listed volumes and for each volume at a specified mount point, such as "/boot".
Total (MB): The amount of storage space available (used and free) across all listed volumes or at the specified mount point. On Linux, the space reserved for root is not counted in the available space.
Free (MB): The amount of unused or free space across all listed volumes or on the selected volume at the specified mount point. On Linux, the space reserved for root is not counted in the available space.
Used (MB): The amount of storage space in use across all listed volumes or on the selected volume at the specified mount point.
Used (%): The percentage of storage space in use across all listed volumes or on the selected volume at the specified mount point.