monitoring.checks.locations

Where checks run from: the control plane and each probe location, its health and the addresses to allowlist

GET /monitoring/api/locationsIAM monitoring:DescribeChecksRead

Every run asks every healthy location at once; a run fails only when `confirmations` locations fail. The control plane does not check Deutsche Cloud’s own addresses.

Request syntax

GET /monitoring/api/locations

Response

200 with one entry per location, { location, healthy, addresses }: the control plane first (always healthy, no addresses listed), then each probe location with an enabled probe, healthy when one was seen recently.

A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.

Errors

  • 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
  • 401No credentials, or an access key that is unknown, revoked or expired.
  • 403The caller's policies do not allow monitoring:DescribeChecks on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
  • 404The resource does not exist in your organization.

Examples

The required parameters only, with example values. Replace id and the other placeholders with your own.

dcloud monitoring checks locations

Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_monitoring_checks_locations.