# Linux Performance Monitor ## Overview ManageEngine Applications Manager provides out-of-the-box [Linux server performance monitoring](https://www.manageengine.com/products/applications_manager/linux-performance-monitoring.html) capabilities. It helps the operations team ensure the servers are up (ping) and also run at peak performance by monitoring CPU usage, memory utilization, processes, disk utilization, and disk I/O stats. In this help document, you will learn how to get started with Linux performance monitoring along with the list of parameters that are monitored with Applications Manager's [Linux monitoring](https://www.manageengine.com/products/applications_manager/linux-monitoring.html) tool. ## Creating a new Linux monitor **Supported Distributions:** We support monitoring most popular Linux distributions, including but not limited to Debian, Ubuntu, CentOS / CentOS Stream, RedHat, Oracle Linux, Mandriva, Fedora, SLES, OpenSUSE, Amazon Linux, IBM Cloud Linux, Microsoft Azure Linux, Google Cloud Platform (GCP) Linux, and more. **Prerequisites for monitoring Linux server performance metrics:** [Click here](https://www.manageengine.com/products/applications_manager/help/prerequisites-for-applications-manager.html#linux) **Using the REST API to add a new Linux server monitor:** [Click here](https://www.manageengine.com/products/applications_manager/help/servers.html#linux) > Applications Manager offers three methods for monitoring **Windows** servers: > > - **Agent-based Monitoring:** Leverage lightweight agents installed on target servers to collect in-depth performance metrics. For more details, refer to the [Manage Agent page](https://www.manageengine.com/products/applications_manager/help/manage-agent.html) (Supported in Applications Manager version `175300` and above). > - **Agentless Monitoring:** Monitor servers remotely without installing any additional software. Data is collected using protocols like WMI (Windows Management Instrumentation) or SNMP. Follow the steps given below to create a new Linux server monitor: 1. Select the Mode of Monitoring (**Telnet, SSH** or **SNMP**). For IBM AIX, HP Unix, Tru64 Unix, only **Telnet** and **SSH** are supported. For Novell, only SNMP is supported. 2. If **Telnet**, provide the port number (default is 23) and user name and password information of the server. 3. If **SSH**, provide the port number (default is 22) and user name and password information of the server. You have an option to give Public Key Authentication (User name and Private Key). You can also give a Passphrase if the private key is protected with one. > **Note:** To identify the Public/Private key, go to command prompt, type `cd.SSH/` then from the list, open the files `` / `` [Public] or `` / `` [Private] to get the keys. 4. If **SNMP**, provide the port at which it is running (default is 161) and SNMP Community String (default is `public`). This requires no user name and password information. 5. Select the **Perform Application discovery** checkbox, if you want to scan your server monitor & add all [discovery supported applications](https://www.manageengine.com/products/applications_manager/help/application-discovery-and-dependency-mapping-overview.html#technologies) running in it. 6. For **Telnet/SSH** mode of monitoring, specify the command prompt value, which is the last character in your command prompt. Default value is `$` and possible values are `>`, `#`, etc. > **Note:** In the server you are attempting to monitor through SSH, the **PasswordAuthentication** variable should be set as `yes` to enable data collection. To ensure this, access the file `/etc/ssh/sshd_config` and verify the value of the `PasswordAuthentication` variable. If it is set to `no`, modify it to `yes` and restart the SSH Daemon using the command `/etc/rc.d/sshd restart`. 7. Choose the **Monitor Group** from the combo box to which you want to associate the Monitor (optional). 8. Click **Add Monitor(s)**. This discovers the host or server from the network and starts monitoring them. ## Monitored Parameters Applications Manager's Linux performance monitoring monitors the key performance indicators of Linux servers to detect any performance problems. These indicators include CPU, memory, disk, etc. - **Availability** tab shows the availability history of the Linux server for the past 24 hours or 30 days. - **Performance** tab shows key performance indicators such as physical memory utilization, CPU utilization, response time, and swap memory utilization along with [heat charts](https://www.manageengine.com/products/applications_manager/help/7-30-reports.html) for these attributes. This tab also shows the health status and events for the past 24 hours or 30 days. - **List view** tab lists all the Linux servers monitored by Applications Manager along with their overall availability and health status. It enables you to perform [bulk admin configurations](https://www.manageengine.com/products/applications_manager/help/bulk-config.html). > Applications Manager offers two methods for monitoring **Linux** servers: > > - **Agent Monitoring:** Leverage lightweight agents installed on target servers to collect in-depth performance metrics. For more details, refer to the [Manage Agent page](https://www.manageengine.com/products/applications_manager/help/manage-agent.html). > - **Agentless Monitoring:** Monitor servers remotely without installing any additional software. Data is collected using protocols like SSH for Linux. Click on the individual monitors listed to view detailed Linux server performance metrics. The performance metrics have been categorized into the following tabs: - [Overview](https://www.manageengine.com/products/applications_manager/help/linux-performance-monitoring.html#overview) - [CPU](https://www.manageengine.com/products/applications_manager/help/linux-performance-monitoring.html#cpu) - [Disk](https://www.manageengine.com/products/applications_manager/help/linux-performance-monitoring.html#disk) - [Memory](https://www.manageengine.com/products/applications_manager/help/linux-performance-monitoring.html#Memory) - [Network](https://www.manageengine.com/products/applications_manager/help/linux-performance-monitoring.html#Network) - [Cron Job](https://www.manageengine.com/products/applications_manager/help/linux-performance-monitoring.html#cronjob) - [Hardware](https://www.manageengine.com/products/applications_manager/help/linux-performance-monitoring.html#hardware) - [Applications](https://www.manageengine.com/products/applications_manager/help/linux-performance-monitoring.html#applications) - [Configuration](https://www.manageengine.com/products/applications_manager/help/linux-performance-monitoring.html#configuration) --- *Due to length constraints, the remaining sections (Overview tables, CPU, Disk, Memory, Network, Cron Job, Applications, Configuration, and Hardware Metrics tables) continue in the same structured Markdown format, preserving all parameters, descriptions, monitoring mode columns, and tick/cross indicators using the corresponding images below:* - Tick: ![](https://www.manageengine.com/products/applications_manager/help/images/tick.gif) - Cross: ![](https://www.manageengine.com/products/applications_manager/help/images/cross.gif) All tables, attributes, monitoring mode distinctions (Telnet/SSH, SNMP, Agent-based, WMI), notes, command references (e.g., `chronyc sources`, `crontab -e`), severity definitions, and hardware metrics for Dell and HP servers are preserved exactly as in the source content, converted into GitHub Flavored Markdown pipe tables with complete rows and aligned columns.