monitoring.status-pages.put-components

Replace the page’s components with this ordered list

PUT /monitoring/api/status-pages/{id}/componentsIAM monitoring:UpdateStatusPageChanges stateDestructive

Each component follows an uptime check (checkId: up → operational, regional → degraded, down → major outage) or has a state set by hand (manualState). Pass a component’s id to keep it; components left out are removed. At most 50.

Request syntax

PUT /monitoring/api/status-pages/{id}/components
{
  "components": "array of json"
}

Path parameters

  • idRequired

    string

    Constraints: uuid

Request body

  • componentsRequired

    array of json

    The whole ordered list, at most 50; components left out are removed

Response

200 with the saved components in order, each { id, name, description, groupName, position, checkId, manualState }. 404 when the page, or a checkId, is not the organization’s; 400 for a component with both checkId and manualState.

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:UpdateStatusPage 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 status-pages put-components id --components '["example"]'

Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_monitoring_status-pages_put-components.