monitoring.alarms.history

The state changes of an alarm, newest first, and who was notified

GET /monitoring/api/alarms/{id}/historyIAM monitoring:DescribeAlarmHistoryRead

Request syntax

GET /monitoring/api/alarms/{id}/history

Path parameters

  • idRequired

    string

    Constraints: uuid

Query parameters

  • limitOptional

    number

    State changes to return, 1–500 (default 100)

    Constraints: integer

Response

200 with up to `limit` state changes, newest first, each { id, alarmId, fromState, toState, reason, notification (what was sent, e.g. "emailed 2, webhook 204", or why nothing was), createdAt }. 404 for a missing alarm 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:DescribeAlarmHistory 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 alarms history id

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