Create your first monitor

Add an uptime check today, the way it actually works right now.

Create your first monitor

A monitor is an outside-in check: upzero probes a URL, port or DNS record on a schedule and records whether it answered. It's one of the "subjects" from Start here. See signals for how a check result relates to the logs, traces and metrics your app sends. The request and response below are real, captured on a local kind cluster; see Install the CLI for why.

No create screen yet

The console doesn't have a monitor list or create page at the time of writing, and the CLI's up0 monitors group only lists monitors and binds them to a service, deliberately not full CRUD. The working path today is the API directly. Both are planned; this page will move to a console walkthrough once one exists.

Create one

Authenticate first (see Install the CLI), then call the API with the same bearer token the CLI stores and your organization id from up0 whoami:

curl <your API URL>/api/v1/me/monitors \
  -H "Authorization: Bearer <your access token>" \
  -H "X-Org-Id: <your org id>" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "1645 example",
    "type": "http",
    "url": "https://example.com",
    "interval_seconds": 300
  }'

A real response, org id shortened:

{
  "id": "5f1ff120-b379-406b-8cee-6c02dd1ed8c5",
  "org_id": "1f1317e4-...",
  "name": "1645 example",
  "type": "http",
  "url": "https://example.com",
  "interval_seconds": 300,
  "status": "pending",
  "last_check_at": null,
  "service_id": null
}

type can be http, tcp, ping, dns or heartbeat. status starts at pending until the first check runs.

Confirm it exists

up0 monitors list
                               Monitors (1 total)
┏━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━┳━━━━━━┳━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━┓
┃ name          ┃ id            ┃ type ┃ status  ┃ url                   ┃ service ┃
┡━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━╇━━━━━━╇━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━┩
│ 1645 example  │ 5f1ff120-b37… │ http │ pending │ https://example.com  │ unbound │
└───────────────┴───────────────┴──────┴─────────┴───────────────────────┴─────────┘

unbound means this monitor isn't linked to a service in your service catalog yet. up0 monitors bind links it to one, once you have one.

What's next

See what happens when something the monitor watches actually breaks: your first issue.

On this page