First Monitor
Step 1: Open the dashboard
Section titled “Step 1: Open the dashboard”
Log in to your OKStatus account. From the main dashboard, click the New monitor button.
Step 2: Configure the HTTP monitor
Section titled “Step 2: Configure the HTTP monitor”Fill in the following fields:
- Name — A descriptive name, e.g. “Main website”.
- URL — The full address to monitor, e.g.
https://example.com. - Method — GET (default) or POST if you need to send a body.
- Interval — Check frequency in seconds (minimum: 30s).
- Expected code(s) — The HTTP status code(s) considered a success, e.g.
200or a range like200-299.
Step 3: Advanced options
Section titled “Step 3: Advanced options”You can also configure:
- Custom headers — Add HTTP headers (e.g.
Authorization). - Keyword check — Verify specific text is present in the response (and optionally invert the check to fail when the text is found).
- JSON query — Resolve a path in a JSON response (
component.status, or$for the raw body) and compare it to an expected value. Keyword and JSON query are the two modes of the Content check selector. - Tags — Free-form labels to organize and filter your monitor list.
- Regions — Select the geographic check locations.
Regions and intervals per plan
Section titled “Regions and intervals per plan”Each region code maps to a real monitoring agent. Codes follow a cc-city
convention (country code + city). Which ones you can select, how many a single
monitor may use, and the shortest interval you’re allowed all depend on your
plan:
| Region code | Location | Minimum plan |
|---|---|---|
fr-dc3 | Paris | Free |
de-fra | Frankfurt | Free |
es-mad | Madrid | Free |
fr-rbx | Roubaix | Pro |
it-mil | Milan | Pro |
uk-lon | London | Pro |
fr-sbg | Strasbourg | Max |
fr-gra | Gravelines | Max |
nl-ams | Amsterdam | Max |
se-sto | Stockholm | Max |
pl-waw | Warsaw | Max |
ch-zrh | Zurich | Max |
ca-bhs | Montréal | Max |
us-hil | Washington DC | Max |
br-sao | São Paulo | Max |
cl-scl | Santiago | Max |
sg-sgp | Singapore | Max |
in-mum | Mumbai | Max |
za-cpt | Cape Town | Max |
za-jnb | Johannesburg | Max |
au-syd | Sydney | Max |
au-mel | Melbourne | Max |
bh-man | Manama | Max |
qa-doh | Doha | Max |
That is 3 regions on Free, 6 on Pro, and all 24 on Max and Enterprise.
| Plan | Minimum interval | Regions per monitor |
|---|---|---|
| Free | 300s (5 min) | 1 |
| Pro | 60s (1 min) | 3 |
| Max | 30s | 5 |
| Enterprise | 30s | 5 |
Enterprise also unlocks the private:<agentId> pseudo-regions served by your
own private agents.
Selecting a region above your plan (from the dashboard, the REST API, or the Terraform provider) is rejected server-side, not silently downgraded.
Step 4: Enable alerts
Section titled “Step 4: Enable alerts”Attach one or more alert channels to this monitor. You’ll be notified as soon as an outage is confirmed (after 1 failed retry by default — configurable per monitor). For each channel you can also choose which alert kinds it should receive: up/down, SSL certificate expiry, and domain expiry.
Click Create to start monitoring immediately.