Monitors

HTTP, TCP, and heartbeat checks. Intervals, regions, tags, SSL expiry, pausing, bulk actions.

Kinds

HTTP monitor

Checks any URL. Configurable:

Method — GET (default), POST, PUT, PATCH, DELETE, HEAD.
Expected status codes — comma list like 200,204 or range 2xx. Default: 2xx.
Headers — arbitrary key/value pairs. Keep secrets out — operators in the org can see them.
Body — for POST/PUT/PATCH. Plain string or JSON.
Follow redirects — default true. Max 5 hops.
Verify TLS — default true. Turn off only for known-bad certs; you lose the SSL-expiry signal.

TCP monitor

Plain dial against host:port. Pass / fail on connect success and configurable connect timeout.

Heartbeat monitor

Inverted. You don’t check anything — your job checks in with Pulse. Each heartbeat monitor exposes a token at /api/v1/heartbeat/<token>. Hit it on every run. If Pulse doesn’t see a beat within interval × tolerance it flips the monitor to down.

Use this for cron jobs, backups, scheduled report runs.

# at the end of your nightly backup
curl -fsS https://pulse.example.com/api/v1/heartbeat/$PULSE_HEARTBEAT_TOKEN

Intervals

Allowed: 60s, 5m, 15m, 30m, 1h. Faster than 60s isn’t supported — Pulse is not a load tester.

Regions and region rule

A monitor can be checked from multiple regions. Each enabled region runs an independent check; the region rule (all / majority / any) decides how to roll the results into a single status. Configure on the monitor’s edit panel.

SSL expiry

Available for HTTP monitors over https://. Pulse remembers the leaf cert’s notAfter from each check. Pair with an alert rule using the SSL expires within trigger to get N-day advance warning.

Pausing

A monitor can be paused — workers stop scheduling it, dashboard shows it as paused, alerts don’t fire. Useful during maintenance windows or while debugging a flapping rule.

Bulk actions

Select multiple monitors on the list page; bulk-pause, bulk-tag, bulk-delete. There is no bulk-create UI; use the API for that.