Scheduling, Alerts & Import/Export

Promote an ObserveOne API Check to a scheduled, multi-region monitor. Set a cron schedule and regions, define assertions, alert on failure through your channels, and export to curl or .http.

A saved check runs on demand with Send. To turn it into a monitor that runs unattended and tells you when an endpoint breaks, use the Schedule, Execution, and Alerts tabs, and define Assertions for what counts as healthy.

Assertions#

On the Assertions tab, define the conditions a response must meet to pass. Each assertion has a type, an operator, and an expected value:

  • Status code, for example equals 200.
  • Response time, for example less than 1000 milliseconds.
  • JSON path, to check a field in a JSON body at a given path.
  • Text contains, to require a substring in the response body.
  • Header, to check a response header value.

Operators include equals, not equals, contains, not contains, greater than, less than, and regex match. A run fails if any assertion fails, and that is what drives alerting.

The Assertions tab with two assertions: status code equals 200, and response time less than 1000 milliseconds.
Assertions define what counts as a healthy response. Any failing assertion fails the run.

Schedule#

On the Schedule tab, set how often the check runs with the frequency control. Once a schedule is on, you can add retries: how many times to retry and how far apart before a run counts as a failure. Retries absorb a transient blip so one flaky response does not page you.

The Schedule tab with the check frequency set to every 5 minutes, plus retry count and retry interval controls.
The Schedule tab sets how often the check runs, with retry count and interval once a schedule is on.

Execution#

The Execution tab controls where and how long a run takes: the regions to run each execution from, and the request timeout. Running from multiple regions shows availability and latency from where your users are, not just from one vantage point.

Alerts#

On the Alerts tab, turn on alert-on-failure and pick the notification channels to fire when the check goes down. Channels are configured once and reused across your checks.

Results#

Once scheduled, each run is recorded per region with its status, latency, and assertion results. Review recent runs from the check's detail view for current health and history.

Export to curl or .http#

Any saved check exports to a curl command or a .http file, with auth and secret references preserved as {{KEY}} placeholders and values stripped. Use it to reproduce the request elsewhere or commit it alongside your code. See the overview for the full export behavior.

Where to go from here#

Was this page helpful?