Simple ping
A curl call at the end of the job is enough for monitoring.
Cron job monitoring
Your job calls a personal ping URL after a successful run. If the heartbeat is missing after its interval and grace period, Clesk Uptime reports the failure.
Cron job · daily at 03:00
Your cron job calls a heartbeat URL after each successful run. If the signal is missing for longer than expected, Clesk Uptime lets you know.
curl https://uptime.clesk.space/ping/…01 / Cron job monitoring
A curl call at the end of the job is enough for monitoring.
Define when a delayed run should actually count as failed.
The same missing heartbeat is not reported repeatedly while it remains down.
Heartbeats reverse normal monitoring: Clesk does not call your service. Your process reports to Clesk after it has completed successfully.
02 / Docs
Set a name, the expected interval and a grace period; you get a personal ping URL.
Chained with && the job only pings on success: your-job.sh && curl -fsS <ping URL>
If the ping stays out, Clesk Uptime reports the failure via your alert channels.
03 / FAQ
Monitoring starts after the heartbeat URL has been called for the first time.
No. A regular HTTP request, for example with curl, is sufficient.
That is what the grace period is for: the alert only fires once interval plus grace are exceeded. Normal variation does not cause false alarms.
Yes. Anything that can send an HTTP request at the end works: cron, systemd, Windows Task Scheduler, CI pipelines.
Clesk Uptime
Create a heartbeat, add the ping URL and define the interval.