Monitoring Mac OS X

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 Mac OS X server, SOASTA CloudTest must be able to establish an SSH connection to the server (a.k.a. "Remote Login"). If you are not sure how to enable this, consult your Mac OS X documentation.

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

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. The Resources step is shown. Check "System Resources" and click Next.

The Hosts/Device Agents screen appears.

Note: The host(s) configured here should be the server(s) running Mac OS X.

  1. Add one or more host(s) that are running Mac OS X.

    1. Select Mac OS X from the list of operating systems, then enter the SSH port number, the user name, and password.
      • Alternately, start a SOASTA Conductor on the server to monitor and then select the Use Conductor on each machine option.
      • Or, specify that you'd like to use a public/private key combination. Refer to Monitoring Using PKI for additional key pair steps.

 

        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 Mac OS X 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 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 the "Network MBits Received" and "Network MBits Sent" statistics, you can enter the name of the network interface you want to monitor (for example, en0 or en1). 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.

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