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.
Please place the extension in the “monitors” directory of your Machine Agent installation directory. Do not place the extension in the “extensions” directory of your Machine Agent installation directory.
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>
The network file mounts to be monitored are configured in config.yml as shown below:
mountedNFS: - fileSystem: "/dev/sdb" displayName: "NFS1" - fileSystem: "/dev/sda" displayName: "NFS2"
Restart the Machine Agent after configuring config.yml as mentioned above.
|nice||niced processes executing in user mode|
|iowait||waiting for I/O to complete|
|system||processes executing in kernel mode|
|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|
|sectors 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||Number of processes|
|runqueue||Processes in run queue|
In addition to the below mentioned metrics for configured mounts, an availability metrics for any external network file system (NFS) mount is reported as well.
|1K-blocks||Number of 1-K blocks|
|used (MB)||Used space|
|available (MB)||Available space|
|used %||Percentage of space used|
The I/O metrics for any external network file system (NFS) mounts are reported:
|op/s||This is the number of operations per second.|
|kB/s||This is the number of kB written/read per second.|
|kB/op||This is the number of kB written/read per each operation.|
|avg RTT (ms)||This is the duration from the time that client’s kernel sends the RPC request until the time it receives the reply.|
|avg exe (ms)||This is the duration from the time that NFS client does the RPC request to its kernel until the RPC request is completed, this includes the RTT time above.|
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 look at the troubleshooting document and make sure that everything is followed correctly.
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 email@example.com.
Always feel free to fork and contribute any changes directly via GitHub.