This extension works only with the standalone machine agent.
The Linux monitoring extension gathers metrics for a Linux machine and sends them to the AppDynamics Metric Browser.
In the AppDynamics Metric Browser, look for: Application Infrastructure Performance | <Tier> | Individual Nodes | <Node> | Custom Metrics | Linux (or the custom path you specified).
Note : Please make sure not to use tab (\t) while editing yaml files. You can validate the yaml file using a yaml validator
Configure the path to the config.yml file by editing the in the monitor.xml file in the
<MACHINE_AGENT_HOME>/monitors/LinuxMonitor/ directory. Below is the sample
<task-arguments> <!-- config file--> <argument name="config-file" is-required="true" default-value="monitors/LinuxMonitor/config.yml" /> .... </task-arguments>
|CPU cores (logical)||Number of CPU cores|
|I/Os currently in progress||Current I/O operations|
|reads completed successfully||Number of successfull reads|
|reads merged||Reads merged|
|sectord read||Sectors read|
|sectors written||Sectors written|
|time spent doing I/Os(ms)||time in ms spent doing I/Os|
|time spent reading(ms)||time in ms spent reading|
|time spent writing(ms)||time in ms spent writing|
|writes completed||Number of writes completed|
|writes merged||Number of writes merged|
|Avg I/O Utilization %||Percentage of CPU time during which I/O requests were issued to the device|
|size (MB)||size (MB)|
|used (MB)||used (MB)|
|available (MB)||available (MB)|
|use %||use %|
|load avg (1 min)||Load average 1 Minute|
|load avg (5 min)||Load average 5 Minute|
|load avg (15 min)||Load average 15 Minute|
|commit limit||Commit limit|
|real free||Real free|
|real free %||Real free percent|
|used %||Used percent|
|receive bytes||Receive bytes|
|receive compressed||Receive compressed|
|receive drop||Receive drop|
|receive errs||Receive errors|
|receive packets||Receive packets|
|transmit bytes||Transmit bytes|
|transmit compressed||Transmit compresses|
|transmit drop||Transmit drop|
|transmit errs||Transmit errors|
|transmit packets||Transmit packets|
|page fault||Page fault|
|page in||Page in|
|page out||Page out|
|swap page in||Swap page in|
|swap page out||Swap page out|
|count||Total number of processes|
|processes||Nnumber of processes|
|runqueue||Processes in run queue|
An availability status for any external network file system (NFS) mounts is reported by executing the command
df | grep <fileSystem> | wc -l.
The storage metrics for any external network file system (NFS) mounts is reported by executing the command
iostat -d <fileSystem>. Following metrics are reported:
|tps||Number of transfers per second issued to the device|
|kB_read/s||Amount of data, in number of blocks(in kilobytes) read from device per second|
|kB_read||The total number of blocks (kilobytes) read|
|kB_wrtn/s||Amount of data written to the device, in a number of blocks (kilobytes) per second|
|kB_wrtn||The total number of blocks (kilobytes) written|
mountedNFS: - fileSystem: "/dev/sdb" displayName: "NFS1" - fileSystem: "/dev/sda" displayName: "NFS2"
Note : By default, a Machine agent or a AppServer agent can send a fixed number of metrics to the controller. To change this limit, please follow the instructions mentioned here. For eg.
java -Dappdynamics.agent.maxMetrics=2500 -jar machineagent.jar
Always feel free to fork and contribute any changes directly via GitHub.
Please visit this page to get detailed instructions on password encryption. The steps in this document will guide you through the whole process.
Workbench is an inbuilt feature provided with each extension in order to assist you to fine tune the extension setup before you actually deploy it on the controller. Please review the following document on How to use the Extensions WorkBench
Please follow the steps listed in this troubleshooting-document in order to troubleshoot your issue. These are a set of common issues that customers might have faced during the installation of the extension. If these don't solve your issue, please follow the last step on the troubleshooting-document to contact the support team.
If after going through the Troubleshooting Document you have not been able to get your extension working, please file a ticket and add the following information.
Please provide the following in order for us to assist you better.
<MachineAgent>/conf/logging/log4j.xml. Change the level value of the following
<logger>elements to debug.
<MachineAgent>/monitors/ExtensionFolderYouAreHavingIssuesWithdirectory here .
For any support related questions, you can also contact firstname.lastname@example.org.
|( Reverting to 2.0.4 from 2.1.0 )|