Atom feed of this document
 
 
 

 v1.0, December 15, 2011

These release notes correspond to the Private Beta for Rackspace Cloud Monitoring.

Product Features

  • Multiple Monitoring Zones Perspective

    Monitor a single resource from many different monitoring zones.

  • Alarm History

    Use an API to retrieve time series data from the system. Use this to go back in time and verify which notifications went out and why.

  • Remote IPv4/v6 Checks

    Monitor IPv4/IPv6 services via IP addresses or using DNS resolution. Using DNS resolution, specify which type of address to resolve, A or AAAA.

  • Data Model

    We’ve disconnected the concept of alerting and data collection so you can create robust and rich monitors. Check many aspects of a single resource; for instance, make sure a site is responding with a 201-status code, and features the copyright as a body match on the bottom of the page.  Ensure all these conditions are met before the status of an alarm is “OK.”

  • Alarm Language

    Create a unique query with our language purposefully built to express thresholds and alert conditions. String compare metrics, use a regular expression operator, check the rate of change, and much more. With each of these primitives you can chain together multiple conditionals to set the state of an alarm. Our documentation highlights best practices for building robust monitors and alarms.

  • On-demand Simulation

    Run a check on-demand, to verify its status before adding it. This allows you to get a feel for a monitor before being alerted by it.  On top of that, you can take the results and pass it another endpoint to simulate your alarm language criteria match!  This is extremely powerful as it takes some of the complexity out of guessing and allows you to simulate responses as they happen in normal operation.

  • Audit Log

    Track all changes to an entity, check and alarm.  Get the before and after of every changed object in the system. You can even add a “who” and “why” parameter to each POST/PUT request to keep a log of why the changes were made.

  • Change Alert Destination

    Depending upon which event is generated, you can execute different notifications; for instance on a warning alert, fire a webhook, but on an error alert, send sysadmin@yourcompany.com an urgent email.

Documentation

Talk to Us

Do you have questions about Rackspace Cloud Monitoring? Would you like to give us feedback on how we're doing?