3.7. Modify an Entity

Let's assume that the IP address for the web server has changed. You can issue a PUT request for only those fields that have changed and the change is reflected in all downstream checks.

Example 3.51. Modify an Entity Request: cURL

curl -i -X PUT \
--data-binary \
'{
   "ip_addresses": {
      "default": "192.168.0.1"
          }
}' \
-H 'X-Auth-Token: auth_token' \
-H 'Content-Type: application/json' \
-H 'Accept: application/json' \
'https://monitoring.api.rackspacecloud.com/v1.0/010101/entities/enn14Ch5mc'

Example 3.52. Modify an Entity Response: cURL

HTTP/1.1 204 No Content
X-Ratelimit-Remaining: 49953
X-Response-Id: .rh-NGRc.h-dfw1-maas-prod-api0.r-AudSFsQj.c-36911.ts-1329412867712.v-b9d7626
Content-Length: 0
X-Lb: dfw1-maas-prod-api1
X-Ratelimit-Type: global
X-Ratelimit-Limit: 50000
Location: https://monitoring.api.rackspacecloud.com/v1.0/010101/entities/enn14Ch5mc
Date: Thu, 16 Feb 2012 17:21:07 GMT
X-Ratelimit-Window: 24 hours
Content-Type: text/plain

Example 3.53. Modify an Entity Request: raxmon

raxmon-entities-update --id=enn14Ch5mc --ip-addresses=default=192.168.0.1

Example 3.54. Modify an Entity Response: raxmon

Resource has been successfully updated

Note that a PUT updates all top level fields. If a top level field contains a hash, the PUT overwrites the entire field. To avoid this, you must specify the complete hash.

NEXT UP: Deleting an entity.

Legal notices