3.2Regions

A region is the place a check runs from. The dashboard calls regions locations. obsrvly offers three regions:

Choose regions#

1. On the create or edit page, find locations in the left column.
2. Select a region to choose it. Select it again to clear it. You can select more than one.
3. Check the line under the regions. It reads, for example, 1 selected · check runs from each. With nothing selected, it reads none selected · the server will use us-west.
4. Save the monitor.

If the list cannot load, the form shows Couldn't load regions — the server will pick one.

What you see#

• The monitor runs one check from each selected region at every interval. Each region gives its own result.
• If any one region fails enough checks to meet the monitor's alert policy, an incident opens. Chapter 9 covers alert policies.
• Each browser check counts as one browser run. That includes each region at each interval. Two regions means twice the runs.

Types without a region picker#

Multi-step API, domain expiry and heartbeat monitors have no locations field in the dashboard. Multi-step API and domain expiry monitors created in the dashboard run from US West. Heartbeat monitors do not run checks from a region.

Set regions with the API#

To list the regions you can use, call ListRegions with the body {}. The response has regions and defaultRegion.

When you create a monitor, send locations. Leave it out, or send [], to use US West:

"locations": ["us-west", "eu-west"]

When you update a monitor, send locations together with replaceLocations: true. Without that flag, obsrvly ignores locations:

{"id": "<monitor-id>",
 "locations": ["us-west", "eu-west"],
 "replaceLocations": true}

If you name a region that obsrvly does not offer, the API returns invalid_argument. The message lists the regions you can use.