As with any commands you will submit to your Cloud resources through the API, you must first authenticate through the API in order for the commands to be correctly processed.
In our Cloud Monitoring Developer's Guide, we show the detailed configuration options available with this service offering, and the necessary components to build functioning monitoring checks. This will require you to work with the following components:
- Account - An account contains attributes describing your account. This description contains mostly read only data; however, a few properties can be modified with the API.
- Entities - An entity is a resource that you want to monitor. Some examples are a server, a website, or a service.
- Checks - Checks explicitly specify how you want to monitor an entity.
- Check Types - These are the available service monitoring checks that you can configure, such as PING, HTTPS, SMTP (and many more).
- Monitoring Zones - A monitoring zone is the "launch point" of a check. You can launch checks from multiple monitoring zones.
- Alarms - An alarm contains a set of rules that determine when a notification is triggered.
- Notifications - A notification is an informational message sent to one or more addresses when an alarm is triggered.
- Notification Plans - A notification plan is a set of notification rules to execute when an alarm is triggered.
See our Cloud Monitoring Developer's Guide for more detailed information about submitting commands through the Cloud Monitoring API.
© 2011-2013 Rackspace US, Inc.
Except where otherwise noted, content on this site is licensed under a
Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License
See license specifics and DISCLAIMER