Monitoring Solaris

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 Solaris 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 Solaris documentation.

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

Supported Versions

SOASTA CloudTest can currently monitor Solaris 10 and later.

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.  The Name and Connection step is shown.
  2. Type a name for the Monitoring Server and optionally provide a description. Finally, type the hostname or IP address of the server into the Host field and click Add. At least one host name must be added before clicking Next.

The Hosts/Device Agents screen appears.

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

  1. The Resources step is shown. Check "System Resources" and click Next.

  1. Select the version of Solaris being monitored, then enter the SSH port number, the user name, and password.

  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 Solaris server. If the connection fails, you will see an error message explaining what went wrong.

  1. Click Next.
  2. Review the information to be sure it is correct, then 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, choose the statistics you want to monitor. For each statistic, you can choose a "sample rate" that determines how often that statistic will be collected.

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

  • For the "Network KBits Received" and "Network KBits Sent" statistics, you can enter the name of the network interface you want to monitor (for example, ni0 or hme1). 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.
  • The "Performance Counter" statistic is specific to Microsoft Windows and should be ignored.

Note: Use the Name (Optional) column to give the metric a user-friendly label that will be used in the widget's title bar whenever this metric appears on a dashboard.

When you are finished, click Next.

Review the information to be sure it is correct, then click Finish.

Next steps

You can also combine database, J2EE, and ColdFusion statistics in the same monitor.

 

Attachments

    Outcomes