norcube monitor
Monitor uptime, SSL certificates and domain expiry, and manage incidents and alerts
Norcube Monitor checks your sites, certificates and domains on a schedule from Norcube's servers. A monitor is an HTTP check (optionally with a keyword), an SSL certificate check or a domain expiry check. Problems confirmed by consecutive checks open incidents, which alert through your alert channels (email, webhook, Slack, Discord, SMS). Status pages show chosen monitors to the public.
Monitors and channels are named by their id or, where a command says so, by their exact name. Checks count towards your Norcube Monitor usage, on a schedule and when you run one now.
In CI, "monitor status --fail-on critical" fails the job while a critical incident is open, and "monitor monitors run <monitor> --wait" fails it when the check finds the monitor down. CI tokens need a Norcube Monitor scope: monitor.read (everything that reads), monitor.check (run checks), monitor.write (manage monitors and incidents), monitor.channels (manage alert channels) or monitor.statuspages (manage status pages and post on them). monitor.write includes neither of the last two.
Usage
norcube monitor <command> [flags]Commands
| Command | Description |
|---|---|
channels | Manage alert channels: email, webhooks, Slack, Discord and SMS |
incidents | List, inspect and acknowledge incidents |
monitors | Create, inspect and manage monitors and their check history |
status | Show the organization's monitoring status, or fail a CI job on open incidents |
status-pages | Manage public status pages, their layout and the incidents posted on them |
Every command also takes the global flags: --profile, --org, -o, --query, --debug and more.
See also
norcube: Command-line interface for the Norcube platform