CLI reference
norcube monitor monitors update
Change a monitor's name, interval or check settings
Not verified yet
Changes only what you pass. Check settings start from the monitor's current ones, so "--timeout 5s" keeps everything else; secret headers keep their stored values unless --secret-headers-file replaces them (and only while the URL keeps its origin). The type can't change. --from-file sends the API's PATCH body as it is (a settings object there replaces the settings as a whole).
Usage
norcube monitor monitors update <monitor> [flags]Examples
norcube monitor monitors update "Shop" --interval 30s --slow 1500ms
norcube monitor monitors update "Shop" --name "Shop (EU)" --expect 2xx,301
norcube monitor monitors update "API cert" --alert-days 21,7
norcube monitor monitors update 7d1c2f7e-6a1f-4f5e-9b8a-1f7c2b3d4e5f --from-file patch.jsonFlags
| Flag | Default | Description |
|---|---|---|
--alert-days | SSL and domain: alert this many days before expiry, up to 5 values (default 30,14,7) | |
--body-content-type | HTTP: Content-Type of --body-file | |
--body-file | HTTP: send the request body read from this file (- for standard input) | |
--cert-expiry-days | HTTP: also watch the certificate, alerting this many days before it expires (https URLs; default on with 30,14,7) | |
--clear-headers | HTTP: remove every request header, secret ones too | |
--description | A note on what the monitor is for | |
--domain | Domain: the registered domain, e.g. example.com (not www.example.com) | |
--domain-expiry-days | HTTP: also watch the domain's registration, alerting this many days before it expires (default on with 30,14,7 for host names) | |
--expect | HTTP: accepted status codes or ranges, e.g. 2xx, 301, 400-404 (repeat or comma-separate; default 2xx) | |
--from-file | Read the request body as JSON from this file (- for standard input), in the API's shape; no other setting flags then | |
--header | HTTP: a request header "Name: value" (repeatable; replaces the plain headers on update) | |
--host | SSL: host whose certificate to check | |
--insecure | HTTP: don't verify the TLS certificate (it is still reported) | |
--interval | 0s | How often to check, e.g. 30s, 5m, 1h (default 1m for HTTP, 1h for SSL, 12h for domains; your organization's limit sets the minimum) |
--keyword | HTTP: text to look for in the response body (the first 256 KiB) | |
--keyword-case-sensitive | HTTP: match the keyword's case | |
--keyword-mode | HTTP: whether the keyword must be present (default) or absent | |
--max-redirects | HTTP: redirects to follow at most (default 5) | |
--method | HTTP: request method (default GET) | |
--name | New name | |
--no-cert-watch | HTTP: don't watch the certificate | |
--no-domain-watch | HTTP: don't watch the domain's registration | |
--no-follow-redirects | HTTP: judge the first response instead of following redirects | |
--no-keyword | HTTP: stop looking for a keyword | |
--port | SSL: port (default 443) | |
--secret-headers-file | HTTP: read secret headers ("Name: value" per line) from this file (- for standard input); stored encrypted, never shown again | |
--server-name | SSL: SNI name to send, when it differs from --host | |
--slow | 0s | HTTP: warn when a response takes longer than this |
--timeout | 0s | HTTP: give up on a request after this long, 1s to 30s (default 10s) |
--url | HTTP: the URL to request |
Every command also takes the global flags: --profile, --org, -o, --query, --debug and more.
See also
norcube monitor monitors: Create, inspect and manage monitors and their check history