Scheduler monitoring
Know the moment a scheduled task misses its window.
What it watches
A scheduler is the inverse of a heartbeat: UpCheck calls your URL on the interval. It's cron as a service, with the alerting already attached.
Point it at an endpoint that does work when called — a cleanup route, a report generator, a queue drain, a cache warmer — and you've replaced the crontab you were going to write, plus the monitoring you were going to forget to put on it.
A trigger, so the rules are stricter
Success is a 2xx, and only a 2xx. Redirects aren't followed: a 3xx means the endpoint moved, and a trigger that lands somewhere else did not do the work you asked for, so it counts as a miss.
There's no fail-streak debounce either. On a health check, one blip that fixes itself is noise worth swallowing. On a trigger, a run that didn't happen is a run that didn't happen, and each result stands on its own.
Write methods only
POST is the default and read-only methods aren't offered, because a trigger has to act. Auth headers and a request body are both supported.
That last part matters more than it sounds: your endpoint is now callable on a schedule by anything that learns the URL. Require a secret header, set it on the scheduler, and reject calls without it.
Point it at something that does work
The endpoint is yours, the cadence is the interval, and the verdict is whatever status you return.
curl -X POST https://upcheck-api-a.rekwiem.com/v1/monitors \
-H "Authorization: Bearer upk_your_key" \
-H "Content-Type: application/json" \
-d '{
"type": "scheduler",
"name": "Hourly rollup",
"url": "https://example.com/cron/rollup",
"interval_sec": 3600
}'Tune it when the defaults aren't right
Highlighted is the default.
Build trust with
public status pages.
Every monitor can back a public status page, so the people asking whether you're down can answer it themselves. Ninety days of history per monitor, on your own domain.
Every outage,
written down as it happens.
A failed check opens an incident on its own, and it keeps a timeline: when it broke, what we saw, when it recovered. Nobody has to remember to write the post-mortem's first half.
Planned downtime
shouldn't page anyone.
Schedule a window and the checks keep running, but the alerts stay quiet and the uptime maths doesn't count it against you. One-off or recurring, per monitor.