This chapter contains a tutorial that will help you become familiar with basic monitoring operations. Examples are provided in cURL with JSON formatting. You can also complete this tutorial by using the Cloud Monitoring command-line interface, raxmon. An example raxmon command is also shown for each operation.
Note
Raxmon is not designed to work on a Windows OS. The tutorial assumes you have a Mac OS.
For the purpose of this tutorial, assume that you have a new web server that you want to ensure is running and responding to requests. Following is the basic workflow for the tutorial:
-
Install and configure raxmon, the Rackspace monitoring command-line interface (CLI).
-
Create an entity to represent the server in the monitoring system.
-
Review the list of monitoring zones.
-
Define three checks for the entity by completing the following tasks in sequence:
-
Set up an email notification and create a notification plan so you can receive information about the entity.
-
Define two alarms by completing the steps in Create an alarm and assign them to a check to begin the monitoring process.
-
Delete the entity and its child objects: the checks and alarms.
Note
In the exercises for this tutorial, include your authorization token where you see
$AUTH_TOKENand your account number where you seeTENANTID.
The first thing you do to begin monitoring a resource is to create an Entity that represents the resource in the monitoring system.
Use the following attributes to create the entity:
label
Assigns a meaningful name to the entity. In the following examples, the server is named My Rackspace Server. You can choose a different name or use the same one, but note that the label is commonly a server name.
ip_address
Specifies the server’s IP address or addresses. In the following examples, the IP address is named “default.”
Note
Remember to insert your authorization token and account number as previously described in Authenticate to the Rackspace Cloud .
Example: Create an entity, request: cURL
curl -i -X POST
--data-binary
'{ "ip_addresses" : { "default" : "192.0.2.15" },
"label" : "My Rackspace Server",
"metadata" : { }
}'
-H 'X-Auth-Token: $AUTH_TOKEN'
-H 'Content-Type: application/json'
-H 'Accept: application/json'
'https://monitoring.api.rackspacecloud.com/v1.0/$TENANTID/entities/'
Example: Create an entity, response: cURL
HTTP/1.1 201 Created
Content-Length: 0
X-Response-Id: .rh-ZWac.h-lon3-maas-prod-api0.r-To4aIzNP.c-25577.ts-1326394448414.v-0c7bb08
X-Powered-By: Express
Location: https://monitoring.api.rackspacecloud.com/v1.0/$TENANTID/entities/enn14Ch5mc
Date: Thu, 12 Jan 2012 18:54:08 GMT
Content-Type: text/plain
If the entity is successfully created, the endpoint returns a response code of 201 Created and a Location header with the URL of the entity. Note that the entity ID is located at the end of the URL. In this example, the entity ID is enn14Ch5mc. Every entity has a unique ID, so yours will be different.
Example: Create an entity, request: raxmon
raxmon-entities-create --label="Monitor Test" --ip-address=default=192.0.2.15
Example: Create an entity, response: raxmon
Resource created. ID: enMlJzlHDo
If an error message is returned, the endpoint was unable to create the entity. See the Faults section.
Note
- For the remaining steps of this tutorial, substitute the ID of the entity that you created for “enn14Ch5mc”.
- You can request a list of all entities for your account at any time. You can also list checks, alarms, notifications, and so on.
Example: List all entities, request: cURL
curl -i -X GET
-H 'X-Auth-Token: $AUTH_TOKEN'
-H 'Content-Type: application/json'
-H 'Accept: application/json'
'https://monitoring.api.rackspacecloud.com/v1.0/$TENANTID/entities'
Example: List all entities, request: raxmon
raxmon-entities-list --details
Listing monitoring zones
Before creating a check for the new entity, choose the Monitoring zones from which you want to run the check. Rackspace Monitoring is server monitored from several monitoring zones to reduce the risk of noisy alarms and check the response time from different locations around the world.
Request a list of the monitoring zones, examine the response, and choose the zone or zones from which you want to launch your first check.
Example: List monitoring zones, request: cURL
curl -i -X GET
-H 'X-Auth-Token: auth_token'
-H 'Accept: application/json'
'https://monitoring.api.rackspacecloud.com/v1.0/010101/monitoring_zones'
Example: List monitoring zones, response: cURL
HTTP/1.1 200 OK
X-Ratelimit-Remaining: 49982
X-Response-Id: .rh-YQzc.h-lon3-maas-prod-api0.r-kCU9r8nq.c-27354.ts-1329332815801.v-3aec925
Transfer-Encoding: chunked
Vary: Accept-Encoding
X-Lb: lon3-maas-prod-api1
X-Ratelimit-Type: global
X-Ratelimit-Limit: 50000
Date: Wed, 15 Feb 2012 19:06:55 GMT
X-Ratelimit-Window: 24 hours
Content-Type: application/json; charset=UTF-8
428
{
"values": [
{
"id": "mzdfw",
"label": "dfw",
"country_code": "US",
"source_ips": [
"2001:4800:7902:0001::/64",
"50.56.142.128/26"
]
},
{
"id": "mzhkg",
"label": "hkg",
"country_code": "HK",
"source_ips": [
"180.150.149.64/26",
"2401:1800:7902:1:0:0:0:0/64"
]
},
{
"id": "mzlon",
"label": "lon",
"country_code": "GB",
"source_ips": [
"2a00:1a48:7902:0001::/64",
"78.136.44.0/26"
]
},
{
"id": "mzord",
"label": "ord",
"country_code": "US",
"source_ips": [
"2001:4801:7902:0001::/64",
"50.57.61.0/26"
]
}
],
"metadata": {
"count": 4,
"limit": 100,
"marker": null,
"next_href": null
}
}
Example: List monitoring zones, request: raxmon
raxmon-monitoring-zones-list --details
Example: List monitoring zones, response: raxmon
{'country_code': u'US',
'driver': <rackspace_monitoring.drivers.rackspace.RackspaceMonitoringDriver object at 0x100562410>,
'extra': {},
'id': u'mzdfw',
'label': u'dfw',
'source_ips': [u'2001:4800:7902:0001::/64', u'50.56.142.128/26']}
{'country_code': u'HK',
'driver': <rackspace_monitoring.drivers.rackspace.RackspaceMonitoringDriver object at 0x100562410>,
'extra': {},
'id': u'mzhkg',
'label': u'hkg',
'source_ips': [u'180.150.149.64/26', u'2401:1800:7902:1:0:0:0:0/64']}
{'country_code': u'GB',
'driver': <rackspace_monitoring.drivers.rackspace.RackspaceMonitoringDriver object at 0x100562410>,
'extra': {},
'id': u'mzlon',
'label': u'lon',
'source_ips': [u'2a00:1a48:7902:0001::/64', u'78.136.44.0/26']}
{'country_code': u'US',
'driver': <rackspace_monitoring.drivers.rackspace.RackspaceMonitoringDriver object at 0x100562410>,
'extra': {},
'id': u'mzord',
'label': u'ord',
'source_ips': [u'2001:4801:7902:0001::/64', u'50.57.61.0/26']}
Any entity that you create can have many checks, each monitoring a different aspect of the entity. In this exercise, you create and test a PING check to verify that the web server is responding. Use the following attributes:
label
Assigns a meaningful name to the check. In the following examples, the check is named “Website check 1”. You can choose a different name or use the same one.
type
Specifies the type of check that you’re creating.
monitoring_zones_poll
Specifies the monitoring zones that will launch the check. The examples use mzdfw.
timeout
Specifies the maximum time Rackspace Monitoring waits for the check to run before considering it to have failed. This value must be less than the value for period.
period
Specifies how often Rackspace Monitoring collectors run the check. This value cannot be less than the value for timeout
target_alias
Resolves the check to an IP address. The example request, next, shows this value as default because that was the name given as the IP address when the entity was created. See the following example for an illustration.
Example: Create a PING check, request: cURL
curl -i
--data-binary
'{ "details" : { },
"label" : "Website check 1",
"monitoring_zones_poll" : [ "mzdfw" ],
"period" : "60",
"target_alias" : "default",
"timeout" : 30,
"type" : "remote.ping"
}'
-H "X-Auth-Token: $AUTH_TOKEN"
-H "Content-Type: application/json"
-H "Accept: application/json"
'https://monitoring.api.rackspacecloud.com/v1.0/$TENANTID/entities/enn14Ch5mc/checks'
Example: Create a PING check, response: cURL
HTTP/1.1 201 Created
Date: Fri, 24 Feb 2012 06:28:51 GMT
Location: https://monitoring.api.rackspacecloud.com/v1.0/$TENANTID/entities/enn14Ch5mc/checks/chyYWNw59I
X-RateLimit-Limit: 50000
X-RateLimit-Remaining: 49969
X-RateLimit-Window: 24 hours
X-RateLimit-Type: global
X-Response-Id: .rh-9pAY.h-lon3-maas-prod-api1.r-2ruPuxLu.c-99739.ts-1330064931513.v-c576983
X-LB: lon3-maas-prod-api1
Content-Length: 0
Content-Type: text/plain
If the check is successfully created, the endpoint returns a response code of 201 Created and a Location: header containing the URL of the check. In this example, the check ID is chyYWNw59I, but yours will be different.
If an error message is returned, see the Faults section section in the Rackspace Cloud Monitoring Developer’s guide.
Note
Checks are always associated with an entity. Therefore all check URLs contain the entity URL. For example, the ID of the entity created earlier in this tutorial is enn14Ch5mc, so the check URLs would begin with https://monitoring.api.rackspacecloud.com/v1.0/010101/entities/enn14Ch5mc/.
Example: Create a PING check, request: raxmon
raxmon-checks-create --entity-id=enn14Ch5mc --type=remote.ping --label="Website check 1" --monitoring-zones=mzdfw --timeout=30 --period=60 --target-alias=default
Example: Create a PING check, response: raxmon
Resource created. ID: chyYWNw59I
Testing the check runs the check once and lists the check’s metrics. This is an easy way to verify and view your metrics. Later, you can use the test check output to help you build alarms.
Example: Create a test check, request: cURL
curl -i
--data-binary
'{ "details" : { },
"label" : "Website check 1",
"monitoring_zones_poll" : [ "mzdfw" ],
"period" : "60",
"target_alias" : "default",
"timeout" : 30,
"type" : "remote.ping"
}'
-H 'X-Auth-Token: $AUTH_TOKEN'
-H 'Content-Type: application/json'
-H 'Accept: application/json'
'https://monitoring.api.rackspacecloud.com/v1.0/$TENANTID/entities/enn14Ch5mc/test-check/'
Example: Create a test check, response: cURL
HTTP/1.1 200 OK
X-Ratelimit-Remaining: 497
X-Response-Id: .rh-VE2m.h-lon3-maas-prod-api0.r-pm6oiwjm.c-37726.ts-1329263604920.v-3aec925
Transfer-Encoding: chunked
Vary: Accept-Encoding
X-Lb: lon3-maas-prod-api1
X-Ratelimit-Type: test_check
X-Ratelimit-Limit: 500
Date: Tue, 14 Feb 2012 23:53:24 GMT
X-Ratelimit-Window: 24 hours
Content-Type: application/json; charset=UTF-8
[
{
"timestamp": 1329263613579,
"monitoring_zone_id": "mzdfw",
"available": true,
"status": "cnt=5,avail=100,min=0.0018,max=0.0020,avg=0.0019",
"metrics": {
"minimum": {
"type": "n",
"data": "1.808000029996e-03"
},
"available": {
"type": "n",
"data": "1.000000000000e+02"
},
"maximum": {
"type": "n",
"data": "1.990000018850e-03"
},
"count": {
"type": "i",
"data": "5"
},
"average": {
"type": "n",
"data": "1.866600010544e-03"
}
}
}
]
Example: Create a test check, request: raxmon
raxmon-checks-test --entity-id=enn14Ch5mc --type=remote.ping --monitoring-zones=mzdfw --timeout=30 --period=60 --target-alias=default
Example: Create a test check, response: raxmon
[{u'available': True, u'timestamp': 1329334696399,
u'monitoring_zone_id': u'mzdfw',
u'status': u'cnt=5,avail=100,min=0.0018,max=0.0020,avg=0.0019',
u'metrics': {u'count': {u'data': u'5', u'type': u'i'},
u'available': {u'data': u'1.000000000000e+02', u'type': u'n'},
u'average': {u'data': u'1.874800003134e-03', u'type': u'n'},
u'minimum': {u'data': u'1.803999999538e-03', u'type': u'n'},
u'maximum': {u'data': u'2.022000029683e-03', u'type': u'n'}}}]
You can list the checks for a specific entity at any time by running a GET request for the entity ID.
Example List all checks for an entity, request: cURL
curl -i -X GET
-H 'X-Auth-Token: auth_token'
-H 'Accept: application/json'
'https://monitoring.api.rackspacecloud.com/v1.0/010101/entities/enn14Ch5mc/checks'
Example List all checks for an entity, response: cURL
HTTP/1.1 200 OK
X-Ratelimit-Remaining: 49967
X-Response-Id: .rh-NGRc.h-dfw1-maas-prod-api0.r-fKxxaymj.c-34581.ts-1329407832952.v-b9d7626
Transfer-Encoding: chunked
Vary: Accept-Encoding
X-Lb: dfw1-maas-prod-api1
X-Ratelimit-Type: global
X-Ratelimit-Limit: 50000
Date: Thu, 16 Feb 2012 15:57:12 GMT
X-Ratelimit-Window: 24 hours
Content-Type: application/json; charset=UTF-8
f37
{
"values": [
{
"id": "chyYWNw59I",
"label": "Website Ping Check",
"type": "remote.ping",
"details": {},
"monitoring_zones_poll": [
"mzord"
],
"timeout": 30,
"period": "60",
"target_alias": "default",
"target_hostname": null,
"target_resolver": null,
"disabled": false,
"collectors": [
"co1LKEam0X"
],
"created_at": 1328285429554,
"updated_at": 1328285429554
},
}
Example List all checks for an entity, request: raxmon
raxmon-checks-list --entity-id=enn14Ch5mc
Example List all checks for an entity, response: raxmon
<Check: id=chyYWNw59I label=Website Ping Check...>
In most cases, you and perhaps several people on your team will be interested in multiple alarms. Rackspace Monitoring lets you set up notification plans that can be shared among multiple alarms. In this exercise, you create the Notifications first, then the notification plan, and then finally the alarms.
Note that to create an alarm, you need a notification plan, and to create a notification plan, you need at least one notification; however, the notifications on the notification plan can be updated or deleted from the plan at any point, even after the plan has been added to an alarm.
A notification specifies how a user will receive informational messages when an alarm is triggered. Notifications can be an email, a webhook, or a page (using PagerDuty), or an SMS text.
Create an email notification, which will be an attribute to the notification plan.
Example: Create a notification, request: cURL
curl -i -X POST
--data-binary
'{ "details" : { "address" : "[email protected]" },
"label" : "Alert email 1",
"type" : "email"
}'
-H 'X-Auth-Token: auth_token'
-H 'Content-Type: application/json'
'https://monitoring.api.rackspacecloud.com/v1.0/010101/notifications'
Example: Create a notification, response: cURL
HTTP/1.1 201 Created
X-Ratelimit-Remaining: 49964
X-Response-Id: .rh-00oi.h-ord1-maas-prod-api1.r-WZWtj0Vc.c-5711.ts-1329408343356.v-b9d7626
Content-Length: 0
X-Lb: ord1-maas-prod-api1
X-Ratelimit-Type: global
X-Ratelimit-Limit: 50000
Location: https://monitoring.api.rackspacecloud.com/v1.0/010101/notifications/nt2T8WtWte
Date: Thu, 16 Feb 2012 16:05:43 GMT
X-Ratelimit-Window: 24 hours
Content-Type: text/plain
Example: Create a notification, request: raxmon
raxmon-notifications-create --label="Alert email 1" --type=email --details=address=[email protected]
Example: Create a notification, response: raxmon
Resource created. ID: nt2T8WtWte
If the notification is successfully created, the endpoint returns a response code of 201 Created and a Location header that contains the URL of the notification. If an error message is returned, the endpoint was unable to create the notification.
A notification represents a single action, such as sending an email to a specific address, whereas a notification plan represents a set of actions. Assuming the ID of the notification that you created is nt2T8WtWte, following is an example of how you might specify the attributes for a notification plan:
label
Specifies a descriptive name for the notification plan.
warning_state
Specifies a list of notification IDs to send when the state is WARNING.
critical_state
Specifies a list of notification IDs to send when the state is CRITICAL.
ok_state
Specifies a list of notification IDs to send when the state is OK.
In this case, you’re configuring the system to send an email when a state changes.
Example: Create a notification plan, request: cURL
curl -i -X POST
--data-binary
'{
"label": "Notification Plan 1",
"warning_state": [
"nt2T8WtWte"
],
"critical_state": [
"nt2T8WtWte"
],
"ok_state": [
"nt2T8WtWte"
]
}'
-H 'X-Auth-Token: $AUTH_TOKEN'
-H 'Content-Type: application/json'
-H 'Accept: application/json'
'https://monitoring.api.rackspacecloud.com/v1.0/$TENANTID/notification_plans'
Example: Create a notification plan, response: cURL
HTTP/1.1 201 Created
X-Ratelimit-Remaining: 49958
X-Response-Id: .rh-ew99.h-dfw1-maas-prod-api1.r-dRuk75SF.c-35593.ts-1329410023443.v-b9d7626
Content-Length: 0
X-Lb: dfw1-maas-prod-api0
X-Ratelimit-Type: global
X-Ratelimit-Limit: 50000
Location: https://monitoring.api.rackspacecloud.com/v1.0/010101/notification_plans/npkmLh5vVk
Date: Thu, 16 Feb 2012 16:33:43 GMT
X-Ratelimit-Window: 24 hours
Content-Type: text/plain
Example: Create a notification plan, request: raxmon
raxmon-notification-plans-create --label="Notification Plan 1" --critical-state=nt2T8WtWte --warning-state=nt2T8WtWte --ok-state=nt2T8WtWte
Example: Create a notification plan, response: raxmon
Resource created. ID: npkmLh5vVk
If the endpoint responds with a 201 Created and a Location header that contains the URL of the new notification plan, the notification plan was created. If the notification plan was not created, an error is returned.
In this exercise, you set an Alarm for the entity. This example alarm sends you a warning alert if the average PING response time is over 50 ms. Remember that alarms always have an entity associated with them; alarm URLs contain the entity URL. In this example, the entity ID is enn14Ch5mc, so you issue the following request to create the alarm and associate it with the entity.
Note
Note You cannot customize the Subject line of an alarm email notification, but you can customize the body as specified in the alarm criteria. In the following example, the “return new AlarmStatus” text in parenthesis, (OK) and (WARNING), can be customized. There is a 16,384 character limit on the criteria attribute.
Example: Create an alarm, request: cURL
curl -i -X POST
--data-binary
'{
"check_id": "chyYWNw59I",
"notification_plan_id": "npkmLh5vVk",
"criteria": "if (metric[\"duration\"] < 50) { return OK } return WARNING"
}'
-H 'X-Auth-Token: $AUTH_TOKEN
-H 'Content-Type: application/json'
-H 'Accept: application/json'
'https://monitoring.api.rackspacecloud.com/v1.0/$TENANTID/entities/enn14Ch5mc/alarms'
Create an alarm, response: cURL
HTTP/1.1 201 Created
X-Ratelimit-Remaining: 49947
X-Response-Id: .rh-ew99.h-dfw1-maas-prod-api1.r-Kti7H0py.c-39599.ts-1329418764114.v-b9d7626
Content-Length: 0
X-Lb: dfw1-maas-prod-api0
X-Ratelimit-Type: global
X-Ratelimit-Limit: 50000
Location: https://monitoring.api.rackspacecloud.com/v1.0/$TENANTID/entities/enn14Ch5mc/alarms/alIxnPKcZp
Date: Thu, 16 Feb 2012 18:59:24 GMT
X-Ratelimit-Window: 24 hours
Content-Type: text/plain
Create an alarm, request: raxmon
raxmon-alarms-create --criteria="if (metric[\"average\"] < 50) { return new AlarmStatus(OK); }
return new AlarmStatus(WARNING);" --check-id=chyYWNw59I --notification-plan=npkmLh5vVk --entity-id=enn14Ch5mc
Create an alarm, response: raxmon
Resource created. ID: alIxnPKcZp
If the endpoint returns a response code of 201 Created and a Location header that contains the URL of the new alarm, the alarm was successfully created; otherwise the endpoint returns an error.
Note that because alarms are shared among all of the checks on an entity, if you have multiple HTTP URLs, you will receive alerts if any of the checks are lagging.
You can list the available alarms as follows.
List alarms, request: cURL
curl -i -X GET
-H 'X-Auth-Token: $AUTH_TOKEN'
-H 'Accept: application/json'
'https://monitoring.api.rackspacecloud.com/v1.0/$TENANTID/entities/enn14Ch5mc/alarms'
List alarms, response: cURL
HTTP/1.1 200 OK
X-Ratelimit-Remaining: 49941
X-Response-Id: .rh-qRGT.h-ord1-maas-prod-api0.r-UH0HesoS.c-404.ts-1329420284585.v-a037e7a
Transfer-Encoding: chunked
Vary: Accept-Encoding
X-Lb: ord1-maas-prod-api0
X-Ratelimit-Type: global
X-Ratelimit-Limit: 50000
Date: Thu, 16 Feb 2012 19:24:44 GMT
X-Ratelimit-Window: 24 hours
Content-Type: application/json; charset=UTF-8
36e
{
"values": [
{
"id": "alIxnPKcZp",
"label": null,
"check_type": "remote.ping",
"check_id": null,
"criteria": "if (metric[\"average\"] < 50) { return new AlarmStatus(OK); } return new AlarmStatus(WARNING);",
"notification_plan_id": "npkmLh5vVk",
"created_at": 1329418764882,
"updated_at": 1329418764882
},
],
"metadata": {
"count": 2,
"limit": 100,
"marker": null,
"next_href": null
}
}
List alarms, request: raxmon
raxmon-alarms-list --entity-id=enn14Ch5mc --details
List alarms, response: raxmon
{'criteria': u'if (metric["average"] < 50) { return new AlarmStatus(OK); } return new AlarmStatus(WARNING);',
'driver': <rackspace_monitoring.drivers.rackspace.RackspaceMonitoringDriver object at 0x100649ad0>,
'entity_id': u'enn14Ch5mc',
'id': u'alIxnPKcZp',
'notification_plan_id': u'npkmLh5vVk',
'type': u'remote.ping'}
Total: 1
The results show there is one alarm for the entity.
Now that you have completed the exercises in this tutorial, you can remove the entity that you created. Removing an entity also removes all associated checks and alarms.
Note
Note To quickly delete an entity and all of its children, use raxmon--entities-delete`. However, you will not be able to manually delete your Rackspace server entities as they are auto-created and deleted by Rackspace automation upon server build/destroy.
Example:Delete an entity, request: cURL
H 'X-Auth-Token: $AUTH_TOKEN'
-H 'Accept: application/json'
'https://monitoring.api.rackspacecloud.com/v1.0/$TENANTID/entities/enn14CH5mc'
Example 2.40. Delete an entity, response: cURL
HTTP/1.1 204 No Content
X-Ratelimit-Remaining: 49984
X-Response-Id: .rh-zyPa.h-dfw1-maas-prod-api0.r-6RuOWE2V.c-236.ts-1330555655887.v-50c8c2d
Content-Length: 0
X-Lb: dfw1-maas-prod-api0
X-Ratelimit-Type: global
X-Ratelimit-Limit: 50000
Date: Wed, 29 Feb 2012 22:47:35 GMT
X-Ratelimit-Window: 24 hours
Content-Type: text/plain
Example 2.41. Delete an entity, request: raxmon
raxmon-entities-delete --id=ENTITY_ID
Example 2.42. Delete an entity, response: raxmon
Resource deleted
Example: Delete checks, request: cURL
curl -i -X
DELETE
-H 'X-Auth-Token: $AUTH_TOKEN'
-H 'Accept: application/json'
'https://monitoring.api.rackspacecloud.com/v1.0/$TENANTID/entities/enn14Ch5mc/checks/chyYWNw59I
Example: Delete checks, response: cURL
HTTP/1.1 204 No Content
X-Ratelimit-Remaining: 49993
X-Response-Id: .rh-Fxp3.h-ord1-maas-prod-api0.r-4Fb5IwLs.c-455.ts-1330554327071.v-50c8c2d
Content-Length: 0
X-Lb: ord1-maas-prod-api1
X-Ratelimit-Type: global
X-Ratelimit-Limit: 50000
Date: Wed, 29 Feb 2012 22:25:27 GMT
X-Ratelimit-Window: 24 hours
Content-Type: text/plain
Example: Delete a check, request: raxmon
raxmon-checks-delete --id=CHECK_ID
Example 2.46. Delete a check, response: raxmon
Resource deleted
Example: Delete alarms, request: cURL
curl -i -X
DELETE
-H 'X-Auth-Token: $AUTH_TOKEN'
'https://monitoring.api.rackspacecloud.com/v1.0/$TENANTID/entities/enn14CH5mc/alarms/alIxnPKczp
Example: Delete alarms, response: cURL
HTTP/1.1 204 No Content
X-Ratelimit-Remaining: 49987
X-Response-Id: .rh-GLyy.h-dfw1-maas-prod-api0.r-2Ulro75y.c-32883.ts-1330554811888.v-6fee2d2
Content-Length: 0
X-Lb: dfw1-maas-prod-api1
X-Ratelimit-Type: global
X-Ratelimit-Limit: 50000
Date: Wed, 29 Feb 2012 22:33:31 GMT
X-Ratelimit-Window: 24 hours
Content-Type: text/plain
Example: Delete an alarm, request: raxmon
raxmon-checks-delete --id=ALARM_ID
Example: Delete an alarm, response: raxmon
Resource deleted