Monitoring Linux

Document created by Chris Sommerstad Employee on Jul 22, 2017Last modified by Dave Murphy on Sep 26, 2017
Version 3Show Document
  • View in full screen mode

Prerequisites

In order to monitor a Linux server, SOASTA CloudTest must be able to establish an SSH connection to the server. If you are not sure how to enable this, consult your Linux documentation.

If a firewall prevents SSH access, see Monitoring a Server Behind a Firewall.

About Memory Utilization on Linux

Like other Linux monitoring tools, including "free" and the GNOME Task Manager, CloudTest monitoring intentionally excludes buffered and cached memory from the total usage statistics presented.  

CloudTest excludes kernel buffers and cache because Linux is

  1. Very aggressive about grabbing all the free RAM for kernel buffers and cache, and
  2. will give it back to user-level programs as soon as needed.  

Without these exclusions, the memory usage would almost always display at 99-100% of the physical RAM on the machine for the reasons above.

Steps

  1. In the Central list, select Monitoring Server Groups.

  1. Click the New Monitoring Server Group icon.

The Monitoring Server / Monitor wizard appears.

  1. Select Monitoring Server Group and click Next.

  1. Type a name for the Monitoring Server Group and optionally provide a description. Click Next.

  1. Check System Resources and click Next.
  2. The Hosts/Device Agents screen appears. Add one or more servers by hostname or IP Address.

Note: The host(s) configured here should be the server(s) running Solaris.

  1. Select the version of Linux to monitor.

  1. Once the Linux version is selected, select a Connection Method. Linux users can use SSH or SOASTA Conductor installed and running on each monitor server in the group.
      • For SSH, enter the port number (usually the default), user name, and password to complete the server group configuration.

      • For the Use Conductor on Each Machine option, ensure that the Conductor is installed and running on each machine you're monitoring.

  1. Click the Test Connection button to test the connection. If the connection is successful, you will see a pop-up containing some information about the Linux server. If the connection fails, you will see an error message explaining what went wrong.

  1. Click Next and review the information to be sure it is correct
  2. Check the "Create a new Monitor for this Monitor Server" box and click Finish.

  1. Enter a name for the Monitor and an optional description, then click Next.

 

    1. Now select the metrics to monitor. For each statistic, you can choose a "sample rate" thatndetermines how often that statistic will be collected.

Some of the statistics require an entry in the "Arguments" column. For example:

    • For the "Network MBits Received" and "Network MBits Sent" statistics, you can enter the name of the network interface you want to monitor (for example, eth0 or eth1). If you do not enter a value, then the total of all network interfaces will be tracked (this excludes the loopback interface).
    • For the "Per Process CPU Percentage", "Per Process Memory Usage", "Per Process Thread Count", and "Per Process Virtual Memory" statistics, you must enter the name of a process (for example, mysqld or httpd). In some cases, there may be multiple matching processes (for example, multiple Apache HTTP worker processes). When this happens, the total for all matching processes will be tracked.

  1. Click Next. Review the monitor configuration, then click Finish.

 

Next steps

Attachments

    Outcomes