Select locations
Monitoring locations are the regions from which ZnowPulse runs checks. Create or edit a monitor and look for Monitoring locations. The app marks locations that have no healthy probe available and locations locked by your plan. Multiple regions require Pro.
Available regions reflect the active monitoring fleet. Do not assume a region exists because it appeared in an old screenshot or configuration. Automation can discover the current list through GET /api/v1/regions with the regions:read scope.
Compare regional evidence
A timeout in one region can have a different cause from a failure in every region. Inspect the monitor's location evidence and recorded times before changing routing or declaring a worldwide outage. Missing regional evidence should not be interpreted as a successful check.
API confirmation policies
The monitor API accepts confirmation_policy alongside regions:
| Policy | Intent |
|---|---|
all_selected |
Require failure confirmation across all selected regions. |
majority |
Confirm failure when at least half the regional observations fail (rounded up). |
any_region |
Allow a failing region to establish failure. |
The default is all_selected. This setting determines how regional observations combine; your alert threshold and maintenance settings still affect delivery. Choose a policy that reflects whether a regional failure is actionable for your service. See the API reference for configuration fields.