CLI reference
norcube monitor status-pages create
Create a status page, unpublished
Not verified yet
Creates a page that nobody can see yet: set what it shows with "layout set", check it with "preview-link", then "publish" it. Every setting is required: the page's public face is your choice, so nothing is filled in for you. A boolean takes =false to turn it off.
Your organization's limit sets how many pages it can have, published or not.
Usage
norcube monitor status-pages create <name> [flags]Examples
norcube monitor status-pages create "Acme status" --slug acme --time-zone Europe/Prague --uptime-days 90 --history-days 90 --show-uptime-bars --show-uptime-percent --show-response-time=false --search-indexingFlags
| Flag | Default | Description |
|---|---|---|
--description | Public text shown under the page's name | |
--history-days | Days resolved incidents stay on the page, 7 to 365 | |
--search-indexing | Let search engines index the page (--search-indexing=false asks them to leave it out) | |
--show-response-time | Show each component's average response time (--show-response-time=false hides it) | |
--show-uptime-bars | Show daily uptime bars (--show-uptime-bars=false hides them) | |
--show-uptime-percent | Show each component's uptime percentage (--show-uptime-percent=false hides it) | |
--slug | The page's public address: 3 to 40 lowercase letters, digits or hyphens | |
--time-zone | IANA time zone the page shows times in, e.g. Europe/Prague | |
--uptime-days | Days the uptime bars cover: 30, 60 or 90 |
Every command also takes the global flags: --profile, --org, -o, --query, --debug and more.
See also
norcube monitor status-pages: Manage public status pages, their layout and the incidents posted on them