Rackspace Monitoring Checks and Alarms
Rackspace Monitoring has several different types of checks with corresponding alarms to choose from. A check determines which aspect of the server you want monitored. The alarm activates based on specific parameters you set on the server.
Checks determine the system to be monitored. You can get a list of available checks by looking at your options in the Check Type menu after clicking the Create Check button in a server’s monitoring page.
NOTE: With General Purpose servers, Rackspace Monitoring will only monitor the system disk. The data disk is not monitored.
The checks are listed in two separate groups:
- Remote service checks: These check types test the Internet connectivity of the servers from remote data centers in regions specified in the check options.
- Agent checks: These checks are performed by the monitoring agent running on your server. They monitor the resource utilization of the server. To learn more, read Install the Rackspace Monitoring Agent.
Check and alarm settings
Each check and alarm has selectable options.
- Check options define what a check will do each time it is executed.
- Alarm options trigger a notification when a check fails.
The checks are defined below. For the official definitions, see the Rackspace Monitoring Developer guide Available Check Types and Fields. Please note, only those checks listed below are available through the control panel. Checks not available in the control panel are noted.
Remote checks are performed from multiple zones. Default zones can be changed.
- HTTP check: This check monitors the URL or IP you choose for
specific HTTP status
or for text in the body of the page (body match).
- HTTP alarm: The standard alarm for the HTTP check is Connection time and Status Code. When the criteria of the alarm is met a notification is issued.
- TCP check: This check monitors a port number on a IP or
hostname you specify.
- TCP alarm: The standard alarm for the TCP check is Connection time. When the criteria of the alarm is met, a notification is issued.
- Ping check: This check sends your server a number of ping
packets that you specify and waits for a response for a set amount
of time. We recommend that 10 packets be sent.
- Ping alarm: The standard alarm for the ping check is Ping packet loss. You can specify what percentage of packet loss must occur for you to be notified.
Remote checks available only in the API or CLI: remote.dns, remote.ftp-banner, remote.imap-banner, remote.mssql-banner, remote.mysql-banner, remote.ping, remote.pop3-banner, remote.postgresql-banner, remote.smtp-banner, remote.smtp, remote.ssh, remote.telnet-banner.
Agent checks are performed by the monitoring agent installed on your server.
- Memory check: This check monitors and displays your server’s
memory use (RAM). It also displays your server’s historical usage.
- Memory alarm: This alarm notifies you when your server memory usage goes above the percentage you set in the criteria.
- CPU check: This check monitors and displays your server’s
CPU usage. It also displays your server’s historical usage.
- CPU alarm: This alarm sends a notification when your CPU usage average exceeds the set criteria.
- Load average check: This check monitors and displays your
system’s load average. This option is most often used with
- Load average alarm: This alarm sends a notification when your system’s load exceeds a number you specify for greater than X number of minutes. X is generally set for 5 minutes.
- File system check: This check monitors and displays disk usage
in a directory that you specify.
- File aystem alarm: This alarm sends a notification when the disk space in your specified directory exceeds the parameter you set.
- Network check: This check monitors your network receiving and
transmitting traffic. The unit of value for this alarm is megabits
per second (Mbit/s). This check also displays your traffic usage.
Unlike the other alarms in this list, you set the network check
alarm variable upon network check creation.
- Network alarm: This alarm sends a notification when either of the network receive or the network transmit rate alarms are triggered.
Continue the conversation in the Rackspace Community.
©2016 Rackspace US, Inc.
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License