A monitoring zone is a location that Rackspace Monitoring
collects data from. Examples of monitoring zones are "US West",
"DFW1" or "ORD1". It is an abstraction for a general location
from which data is collected.

An endpoint, also known as a collector, collects data from the monitoring
zone. The endpoint is mapped directly to an individual computer or a virtual
machine. A monitoring zone contains many endpoints, all of which will be within
the IP address range listed in the response. The opposite is not true, however,
as there may be unallocated IP addresses or unrelated machines within that IP
address range.

A check references a list of monitoring zones it should be run from.

Attributes

Name

Description

Validation

country_code

Country Code

String longer than 2
characters

label

Label

String

Non-empty string

source_ips

Source IP list

Array [String]

Use the following monitoring zones API operations to get information about
monitoring zones and to run traceroutes.

For Private Network Monitoring, API operations are included to create, update,
and delete private monitoring zones.

This API operation lets you run a traceroute from a monitoring zone
to a Hostname or IP address. Like all Cloud Monitoring features,
the Traceroute API is fully dual stack, supporting both IPv4 and IPv6.
The Traceroute API can be used to debug networking issues between
the Cloud Monitoring collectors and your infrastructure.

Note

Hop numbers can repeat, which indicates a split in the route.

The following table shows the possible response codes for this operation:

Response Code

Name

Description

200

OK

Request completed.

401

Unauthorized

The system received a
request from a user that
is not authenticated.

403

Forbidden

The system received a
request that the user is
not authorized to make.

Updates the private monitoring zone specified by monitoringZoneId. You
can make partial updates to a private monitoring zone. When you submit the
update request, only specify the parameters that you want to update.

The following table shows the possible response codes for this operation:

Response Code

Name

Description

204

OK

The server has fulfilled
the request but does not
need to return an entity-
body.

400

Bad request

The system received an
invalid value in a
request.

401

Unauthorized

The system received a
request from a user that
is not authenticated.

403

Forbidden

The system received a
request that the user is
not authorized to make.