CLI reference
norcube monitor status-pages incidents update
Correct a posted incident; public within a minute on a published page
Not verified yet
Corrects a post's title, impact, start or references, and changes only what you pass. It adds no update and doesn't move the status: for that, use "incidents updates create". --component replaces the affected components as a whole. Resolved posts can be corrected too. On a published page a correction is public within a minute.
Usage
norcube monitor status-pages incidents update <page> <incident> [flags]Examples
norcube monitor status-pages incidents update acme 8c7d6e5f-4a3b-4c2d-9e1f-0a1b2c3d4e5f --title "Elevated API errors in Europe"
norcube monitor status-pages incidents update acme 8c7d6e5f-4a3b-4c2d-9e1f-0a1b2c3d4e5f --impact major --component "API=partial_outage"Flags
| Flag | Default | Description |
|---|---|---|
--component | An affected component and the status the page shows it in while the incident is open, as "<id or name>=<status>" (repeatable): operational, degraded_performance, partial_outage or major_outage | |
--impact | New impact: none, minor, major or critical | |
--monitor-incident | Replace the linked monitor incidents with these ids (repeat or comma-separate); never published | |
--no-components | Remove every affected component | |
--no-monitor-incidents | Remove every link to a monitor incident | |
--started-at | When it began: an RFC 3339 timestamp, a date or an age (20m, 2h) | |
--title | New public title |
Every command also takes the global flags: --profile, --org, -o, --query, --debug and more.
See also
norcube monitor status-pages incidents: Post incidents on a status page and keep them updated