Monitor templates and recipes
Save monitor configurations and use built-in recipes.
Templates save a monitor's complete configuration so you can reuse it without retyping. Recipes are built-in starting points for common checks. Open the Templates dialog from the Monitors page toolbar.
Built-in recipes
The Built-in recipes section provides preset configurations that can be edited:
| Recipe | Starts with |
|---|---|
| Website availability | HTTPS GET with redirects, TLS verification, and a 2xx response |
| JSON API health | API health endpoint with JSON response validation and retries |
| Certificate expiry | TLS handshake, trust validation, and a 30-day expiry warning |
| DNS resolution | Require an A record through the worker's configured resolvers |
| Database connection | Open a PostgreSQL connection and verify the server is reachable |
| Scheduled heartbeat | Expect a push every five minutes with a five-minute grace period |
Choosing a recipe opens the normal editor with the configuration pre-filled, so you can review and test the target and assertions before creating the monitor.
Save a template
In the Save template section, enter a unique template name, choose a source monitor, and select Save template. The complete configuration is copied, including protocol settings, assertions, credentials, retries, regions, schedules, and taxonomy. Dependencies are omitted so reusing a template cannot bind new monitors to an unrelated dependency graph.
Templates can contain request credentials. Treat them as sensitive configuration.
Apply a template
The Bulk create section lists your saved templates. Two ways to use one:
- Use in editor opens a new unsaved monitor draft populated from the template. Review and change the name or any setting before creating it.
- Create monitors accepts one unique monitor name per line (1–100 names) and creates the whole batch atomically.
Heartbeat monitors created from templates receive independent one-time credentials. All generated push URLs are presented together once after the batch succeeds; store them immediately.
Use Delete template to remove one you no longer need. Deleting a template does not affect monitors already created from it.