Browse docs
On this page

Getting Started

This guide walks through creating a monitor that checks response correctness across regions and alerts your team when checks fail.

1. Create a Monitor

In the dashboard, go to Monitors and select Create Monitor.

Provide:

  • Name
  • URL (full endpoint)
  • HTTP method
  • Check frequency
  • Timeout

2. Choose a Frequency

Current monitor intervals are:

  • 60 seconds (1 minute)
  • 120 seconds (2 minutes)
  • 180 seconds (3 minutes)
  • 240 seconds (4 minutes)
  • 300 seconds (5 minutes)
  • 600 seconds (10 minutes)
  • 900 seconds (15 minutes)
  • 1800 seconds (30 minutes)
  • 3600 seconds (60 minutes)

3. Configure the Request

Supported body types:

  • none
  • json
  • form
  • graphql

You can add custom headers and request body fields before checks run.

See Request Configuration.

4. Select Regions

Regions supported:

  • us-east-1 (Virginia)
  • us-west-1 (Oregon)
  • eu-central-1 (Frankfurt)
  • ap-southeast-1 (Singapore)
  • ap-southeast-2 (Sydney)
  • sa-east-1 (Sao Paulo)

Use at least two regions for production APIs so a single-region network issue does not hide failures.

See Regions.

5. Add Assertions

Default monitor creation starts with a status code assertion (equals 200).

Add additional checks such as:

  • JSON path value checks
  • Response time thresholds
  • Header assertions
  • Regex body matches
  • Existence checks

See Assertions.

6. Attach Alert Channels

Create channels under Alert Channels and attach them to monitors.

Supported channel types:

  • Email
  • Slack
  • Discord
  • Webhook
  • PagerDuty

See Alert Channels.

7. Monitor Incident Lifecycle

When checks fail, monitor status transitions to down and incidents are created/resolved automatically based on subsequent checks.

See Incidents.

Next Steps