CLI reference
norcube monitor status-pages incidents create
Post an incident on a status page; public within a minute on a published page
Not verified yet
Posts an incident with its first update. On a published page it is public within a minute: write it for your customers. It counts toward the page's overall status while it is open, and --component sets what the page shows for the components it affects.
--monitor-incident links the monitor incidents the post is about, for your own navigation; the links are never published.
Usage
norcube monitor status-pages incidents create <page> [flags]Examples
norcube monitor status-pages incidents create acme --title "Elevated API errors" --status investigating --impact minor --message "We are looking into it."
norcube monitor status-pages incidents create acme --title "Checkout is down" --status identified --impact major --message-file update.txt --component "Checkout=major_outage" --started-at 20mFlags
| 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 | How bad it is: none, minor, major or critical | |
--message | The first update's text; public | |
--message-file | Read the message from this file (- for standard input) | |
--monitor-incident | Id of a monitor incident this post is about (repeat or comma-separate); never published | |
--started-at | When it began, if not now: an RFC 3339 timestamp, a date or an age (20m, 2h) | |
--status | Where it stands: investigating, identified, monitoring or resolved | |
--title | The incident's 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