monitoring incidents
Lists the incidents on your status page, newest first, with each one's status, impact, when it started and how many updates it has. What you post is public as soon as it's written: there's no draft and no publish.
octri monitoring incidents [list | show | create | post | resolve | update | delete]Flags
--openbooleanLeaves out resolved incidents.
octri monitoring incidents show <id>
Prints one incident and its timeline, oldest update first.
Arguments
<id>stringrequiredThe incident.
octri monitoring incidents create <title>
Opens an incident.
Arguments
<title>stringrequiredWhat readers see as the headline.
Flags
--message <text>stringrequiredThe first update readers see.
--status <status>stringinvestigating, identified, monitoring or resolved.
--impact <impact>stringminor, major, critical or maintenance.
--checks <ids>listThe IDs of the checks it affects.
octri monitoring incidents post <id>
Adds an update to the timeline.
Arguments
<id>stringrequiredThe incident.
Flags
--message <text>stringrequiredThe update's text. The words after the ID work too.
--status <status>stringMoves the incident on, such as to identified.
octri monitoring incidents resolve <id>
Posts the closing update and marks the incident resolved.
Arguments
<id>stringrequiredThe incident.
Flags
--message <text>stringThe closing update.
octri monitoring incidents update <id>
Changes the incident itself rather than its timeline.
Arguments
<id>stringrequiredThe incident.
Flags
--title <text>stringA new headline.
--impact <impact>stringA new impact.
--checks <ids>listReplaces the affected checks.
octri monitoring incidents delete <id> --yes
Deletes the incident and every update on it. Resolve it instead to keep the record.
Arguments
<id>stringrequiredThe incident.
Flags
--yesbooleanrequiredConfirms the delete.
Examples
Open an incident
octri monitoring incidents create "Elevated checkout errors" --message "We are seeing failed payments and are looking into it." --impact major✔ Opening the incident
✔ Incident Elevated checkout errors is on the status page (7fbbea1a-b853-4e71-83a6-8d3ce75fd940)
octri monitoring incidents post 7fbbea1a-b853-4e71-83a6-8d3ce75fd940 --status identified --message "…"Post an update
octri monitoring incidents post 7fbbea1a-b853-4e71-83a6-8d3ce75fd940 --status identified --message "A bad deploy. Rolling back now."✔ Posting the update
✔ Posted to Elevated checkout errors: now identifiedResolve it
octri monitoring incidents resolve 7fbbea1a-b853-4e71-83a6-8d3ce75fd940✔ Resolving
✔ Elevated checkout errors is resolved.Read the timeline
octri monitoring incidents show 7fbbea1a-b853-4e71-83a6-8d3ce75fd940✔ Loading incident
Elevated checkout errors
status resolved
impact major
started 1s ago
resolved 0s ago
investigating 1s ago · Dana Reyes-Park
We are seeing failed payments and are looking into it.
identified 1s ago · Dana Reyes-Park
A bad deploy. Rolling back now.
resolved 0s ago · Dana Reyes-Park
This incident has been resolved.Related
octri monitoring announcements: Banners on your status page, such as planned maintenance.octri monitoring checks: Uptime checks: generate them from your spec and run one now.