Ping check. Monitors server communication and response times. Reports the traceroute path—listing all intermediate servers (or "hops") between the remote monitoring server and the target server—so you can measure traffic path efficiency.
HTTP check. Connects to the web server and retrieves specific content to verify that users can see and interact with your application. This check can also follow redirects and confirm that users can log into your website.
SSH check. Confirms that the target server’s secure shell (SSH) protocol is running and accepting requests, and measures the response time. Also, identifies the SSH fingerprint and notifies you if it changes or becomes corrupted.
HTTPS check. Monitors the validity of the Secure Socket Layer (SSL) certificate by transmitting HTTP packets over the SSL protocol and verifying security-related information based on the return payload.
DNS check. Confirms that the target domain name server (DNS) can accurately resolve a submitted URL to the correct IP address(es), so that visitors can view your website.
Email server check. Connects to the SMTP (outgoing) email server, and verifies that emails can be sent. It can also retrieve metrics about server capabilities.
Retrieves an automatic response from the server to confirm that the expected port is open, taking requests, and initiating communication. Remote banner monitoring supports SSL and works for systems and databases (MS SQL, MySQL, and PostgreSQL).
Since the agent reports metrics from inside your server, it can provide rich information that isn’t available from the hypervisor—so you can diagnose problems more effectively.
CPU: Discover if your server’s CPU is being heavily utilized by the kernel, your code, or other processes on the same host.
Load average: Monitor your load average (in 1-, 5-, or 15-minute intervals) to know the average system load over a period of time.
Memory: Know when your application is consuming too much memory, and how much of it is being consumed by the operating system.
File system: Monitor any file system, including Cloud Block Storage volumes, and get alerted if you’re running out of space or available i-nodes.
Disk: Measure input/output operations per second (IOPS) and throughput, so you can identify bottlenecks with greater precision.
Network: Detect network errors, collisions, overruns, and dropped packets, so you can diagnose network interface problems.
The Cloud Monitoring Agent serves your platform components, including databases like MySQL or MSSQL and web servers like Apache.
Apache check. Reports metrics such as the number of worker threads, uptime, and requests per second.
MySQL check. Reports metrics such as row locks, buffer pools, and connection counts. Also applied automatically to all Cloud Databases instances.
Redis check. Monitors the popular NoSQL database for connection counts, evicted keys, and ongoing operations, among others.
Through the Cloud Monitoring Agent’s plugin framework, you can monitor any aspect of your infrastructure or application. Check out our plugins repository to see if your application is already supported.
Our easy-to-use alarm language allows you to write very concise thresholds, set conditions, apply functions on data, and more.
Provides generic notification integration for customization purposes.
Send email notifications that contain alarm state information and context for the alarm.
Send SMS notifications to your mobile device, anywhere you have service, including to international numbers. Unlimited free SMS are included with every Cloud account. Standard carrier rates for SMS apply.
PagerDuty is a SaaS-based operations performance platform that includes smart alerting and escalation, on-call scheduling and incident reporting. Through PagerDuty notification from Cloud Monitoring, you can ensure the right people for the problem are alerted to decrease resolution times. For details, please see http://pduty.me/rax-pagerduty.
Silence specific alerts for a period of time, such as during scheduled maintenance.
Collect monitoring data as often as once every 30 seconds.
Cloud Monitoring retains full resolution data for at least 2 days to support Root Cause Analysis (RCA). It periodically consolidates full-resolution data points into coarser data points, which it retains for longer periods of time to support trending analysis. The longest retention times are for daily data, which is at least one year.
Through API and CLI, you can conduct advanced host interrogation from wherever you are, without the need to log into the server.
System configurations. Confirm the operating system version, check out available network and disk devices, mounted filesystem, and available CPU and memory.
System performance. Retrieve current information for compute, memory, disk, and networking.
Processes and users. Retrieve detailed information about currently running processes and logged-in users.
Agent Linux binaries and repositories are signed using public key cryptography, and verified using native distribution methods.
Agents connect to Cloud Monitoring instances in three data centers using Transport Layer Security (TLS). The agents are packaged with (and trust only) a single root CA certificate that is directly under Rackspace control.
The monitoring agent gathers metrics about your system, and it specifically does not run arbitrary commands. This means that even if your API token is compromised, the only thing an attacker can access is your metrics.
Agent updates are verified against a cryptographic digest that is signed by the agent root certificate authority. The signing certificate is separate from the endpoint TLS certificate, and signing is done offline on a single machine. This means that update security is separated from the endpoint.
Sign up for a cloud account to start customized monitoring today.
Get instant help and information from blogs, documentation, white papers, and more.