CLI reference
norcube monitor monitors alerts set
Set where and when a monitor alerts
Not verified yet
Replaces the monitor's alerting. --defaults returns it to the organization's defaults. Otherwise give its routes, each a channel (id or exact name) and the events it gets (down, warning, expiring, expired, recovered), or --mute for no alerts; settings you leave out keep their current values. Channels themselves are managed with "monitor channels".
Usage
norcube monitor monitors alerts set <monitor> [flags]Examples
norcube monitor monitors alerts set "Shop" --route "On-call webhook=down,recovered" --route ops-email=down
norcube monitor monitors alerts set "Shop" --confirm-failures 3 --reminder 30m
norcube monitor monitors alerts set "Shop" --mute
norcube monitor monitors alerts set "Shop" --defaultsFlags
| Flag | Default | Description |
|---|---|---|
--confirm-failures | Failed checks in a row before an incident opens, 1 to 10 | |
--confirm-successes | Good checks in a row before it resolves, 1 to 10 | |
--defaults | Follow the organization's default channels again | |
--from-file | Read the API's alert settings body as JSON from this file (- for standard input) | |
--mute | Send no alerts for this monitor | |
--reminder | 0s | Remind about an unacknowledged critical incident this often, e.g. 1h (0 for no reminders) |
--route | A route "<channel>=<event>,<event>" (channel id or exact name; events down, warning, expiring, expired, recovered); repeatable, replaces the routes |
Every command also takes the global flags: --profile, --org, -o, --query, --debug and more.
See also
norcube monitor monitors alerts: Where and when a monitor alerts