Exporting Monitors
You can export all of your team's monitors to a CSV file from the
Monitors page. Click the Export button in the
page header to download a file named
monitors-export-YYYY-MM-DD.csv.
The exported CSV can be opened directly in Excel, Google Sheets, Numbers, or any text editor. This makes it easy to review, edit, or back up your monitor configuration before making bulk changes or downgrading your plan.
HTTP Monitors Only
Import and export currently cover HTTP monitors. Ping, TCP port, heartbeat and cron monitors aren't included in the CSV — create or edit those in the UI or via the REST API.
CSV Format Reference
The CSV uses a header row followed by one row per monitor. Array values are
pipe-delimited (value1|value2)
and JSON fields are stored as JSON strings within the cell.
| Column | Required | Description | Example |
|---|---|---|---|
| url | Yes | Full URL to monitor | https://example.com |
| friendly_name | No | Display name for the monitor | My Website |
| check_interval | No | Minutes between checks (default: 5) | 1 |
| check_types | No | Pipe-delimited check types | uptime|ssl|dns |
| monitored_regions | No | Pipe-delimited region codes | ash|pdx|nbg|sin |
| http_method | No | HTTP method (default: GET) | GET |
| request_timeout | No | Timeout in seconds (default: 30) | 30 |
| accepted_status_codes | No | Pipe-delimited status codes | 2xx|3xx |
| follow_redirects | No | Follow HTTP redirects (default: true) | true |
| slow_response_threshold | No | Slow response threshold in ms | 2000 |
| ssl_expiry_threshold | No | Days before SSL expiry to alert | 30 |
| domain_expiry_threshold | No | Days before domain expiry to alert | 30 |
| status_page_enabled | No | Enable public status page | false |
| status_page_slug | No | URL slug for the status page | my-website |
| status_page_title | No | Title shown on the status page | My Website Status |
| keyword_settings | No | JSON string with keyword config | {"keyword":"OK"} |
| notification_settings | No | JSON string with notification config | {"email":true} |
| tags | No | Pipe-delimited tag names | production|client-a |
Importing Monitors
To import monitors, click the Import button on the Monitors page
and select a CSV file. The file must include a header row with at least a
url
column. All other columns are optional and will use sensible defaults when omitted.
Import Rules
- Duplicates are skipped — if a monitor with the same URL already exists on your team, the row is skipped.
- Plan limits are enforced — importing stops once your plan's monitor limit is reached.
- Tags are created automatically — any tag names in the CSV that don't already exist will be created.
- New monitors start in "pending" status — they will be checked on the next monitoring cycle.
Example CSV
Here is a minimal example with three monitors. You can also download a sample CSV with all columns included.
Tip
The easiest way to prepare an import file is to first export your existing monitors, then use that file as a template. Edit the rows in Excel or Google Sheets and re-import.
Security Note
HTTP authentication credentials (auth_username,
auth_password)
are excluded from exports for security. If your monitors use HTTP authentication,
you will need to re-enter those credentials after importing.