norcube monitor channels
Manage alert channels: email, webhooks, Slack, Discord and SMS
Alert channels are where incidents alert. Default channels get the alerts of every monitor that follows the organization's defaults; a monitor's own routes ("monitors alerts set") name channels directly.
Credentials stay secret: Slack and Discord URLs are read from a file or standard input and shown only as a hint, and a webhook's signing secret is written to a file you name, never printed. Email-address and SMS channels get no alerts until their contact confirms a code ("channels verify"). A CI token changes channels only with the monitor.channels scope (monitor.write doesn't include it); any Norcube Monitor scope reads them.
Usage
norcube monitor channels <command> [flags]Also available as: channel, alert-channels.
Commands
| Command | Description |
|---|---|
create | Create an alert channel |
delete | Delete an alert channel |
deliveries | The alerts a channel was given to send |
get | Show an alert channel |
list | List alert channels |
test | Send a test alert through a channel now |
update | Rename, enable, disable or reconfigure an alert channel |
verify | Confirm an SMS or email-address channel with the code sent to it |
Every command also takes the global flags: --profile, --org, -o, --query, --debug and more.
See also
norcube monitor: Monitor uptime, SSL certificates and domain expiry, and manage incidents and alerts