monitoring.checks.outages

The outage log of a check, newest first, with who was notified

GET /monitoring/api/checks/{id}/outagesIAM monitoring:GetCheckResultsRead

Request syntax

GET /monitoring/api/checks/{id}/outages

Path parameters

  • idRequired

    string

    Constraints: uuid

Query parameters

  • limitOptional

    number

    1–500, default 50

    Constraints: integer

Response

200 with up to `limit` outages, newest first, each { id, startedAt, endedAt (null while open), cause, failedLocations, downNotification, upNotification }. 404 for a missing check and for one the caller may not read.

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:GetCheckResults 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 outages id

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