Documentation
Everything you need to set up monitoring, route alerts and integrate Pulwatchers with your services.
Quick start
Create your first check in three steps:
- Sign in and open Checks → New check.
- Enter a URL or host, choose an interval and add assertions (status code, latency or a keyword).
- Pick the alert channels that should fire when the check fails.
Heartbeat monitoring
For cron jobs, queue workers and other tasks that aren't reachable from outside, use a heartbeat. Pulwatchers gives each heartbeat a unique, opaque token URL. Your job pings it on success; if a ping doesn't arrive within the expected window, we raise an incident.
Send a lightweight GET (or POST) at the end of a successful run:
curl -fsS https://updates.pulwatchers.com/sub/<heartbeat-token> > /dev/null
The token is a random, unguessable identifier — treat it like a secret. A request to an unknown token returns 404. Typical crontab usage:
# run backup, then check in with Pulwatchers 0 3 * * * /usr/local/bin/backup.sh && curl -fsS https://updates.pulwatchers.com/sub/9f2c… > /dev/null
You can set a grace period per heartbeat so a job that occasionally runs long doesn't trigger a false alarm.
Alerting
Each check or heartbeat can notify one or more channels: email, webhook, Slack, Telegram and PagerDuty. Use escalation policies to page the next responder if the first doesn't acknowledge.
API
Manage monitors programmatically with scoped API tokens. List your checks:
curl -H "Authorization: Bearer <api-token>" https://api.pulwatchers.com/v1/checks
Status pages
Publish a branded status page so customers can self-serve during an incident. Subscribers receive automatic updates when you open, update or resolve an incident.