CLI reference

norcube monitor channels create

Create an alert channel

Not verified yet

Creates a channel of one kind:

email    --address (confirmed with a code sent there) or --members
webhook  --url; signed with a secret Norcube Monitor generates (saved with
         --secret-file, never printed) or yours (--signing-secret-file)
slack    --url-file: the incoming-webhook URL, from a file or stdin
discord  --url-file: the webhook URL, from a file or stdin
sms      --phone (confirmed with a code texted there)

Email-address and SMS channels get no alerts until verified: run "channels verify <channel>" (on a terminal it asks for the code).

Usage

norcube monitor channels create <name> [flags]

Examples

norcube monitor channels create "Ops" --kind email --address [email protected] --default
norcube monitor channels create "On-call webhook" --kind webhook --url https://example.com/hooks/monitor --secret-file webhook-secret.txt
pbpaste | norcube monitor channels create "#alerts" --kind slack --url-file -
norcube monitor channels create "On-call phone" --kind sms --phone +420601123456

Flags

FlagDefaultDescription
--addressemail: the address to alert (it gets a code to confirm)
--defaultMake it a default channel: monitors that follow the organization's defaults alert here
--kindChannel kind: email, webhook, slack, discord or sms
--membersemail: alert the organization's members instead of one address
--phonesms: a mobile number in international format, e.g. +420601123456 (it gets a code to confirm)
--secret-filewebhook: write the generated signing secret to this new file (mode 0600); it is never printed
--signing-secret-filewebhook: use your own signing secret (whsec_…) read from this file (- for standard input)
--urlwebhook: the URL Norcube Monitor posts signed alerts to
--url-fileslack, discord: read the incoming-webhook URL (a credential) from this file (- for standard input)

Every command also takes the global flags: --profile, --org, -o, --query, --debug and more.

See also

On this page