monitoring.incidents.update

Post an update to an incident; status resolved closes it. Subscribers are told

POST /monitoring/api/status-pages/{id}/incidents/{incidentId}/updatesIAM monitoring:UpdateIncidentChanges state

Request syntax

POST /monitoring/api/status-pages/{id}/incidents/{incidentId}/updates
{
  "status": "enum",
  "body": "string",
  "impact": "enum"
}

Path parameters

  • idRequired

    string

    Constraints: uuid

  • incidentIdRequired

    string

    Constraints: uuid

Request body

  • statusRequired

    enum

    The incident’s status from now on: resolved closes it; any other status reopens a resolved incident

    One of: investigating, identified, monitoring, resolved

  • bodyRequired

    string

    Plain text, up to 5000 characters

  • impactOptional

    enum

    none, minor (degraded), major (partial outage), critical (major outage); unchanged when omitted

    One of: none, minor, major, critical

Response

200 with the incident as list describes it, the new update last, plus notified (what was sent to subscribers). 404 when the page or the incident does not exist.

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:UpdateIncident 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 incidents update id incidentId --status investigating --body example

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