Simple ping
A curl call at the end of the job is enough for monitoring.
← Clesk Uptime
Cron job monitoring
A silent cron failure does not have to remain unnoticed until tomorrow.
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.
Interval plus grace
Define when a delayed run should actually count as failed.
One alert per outage
The same missing heartbeat is not reported repeatedly while it remains down.
For everything without a public endpoint
Heartbeats reverse normal monitoring: Clesk does not call your service. Your process reports to Clesk after it has completed successfully.
- ✓Database and file backups
- ✓Imports, exports and synchronizations
- ✓Newsletter, invoice and reporting jobs
Set up in three steps
- 1
Create the heartbeat
Set a name, the expected interval and a grace period; you get a personal ping URL.
- 2
Append the ping to your job
Chained with && the job only pings on success: your-job.sh && curl -fsS <ping URL>
- 3
Silence becomes an alert
If the ping stays out, Clesk Uptime reports the failure via your alert channels.
FAQ
What happens before the first ping?
Monitoring starts after the heartbeat URL has been called for the first time.
Do I need an SDK?
No. A regular HTTP request, for example with curl, is sufficient.
What if my job takes a varying amount of time?
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.
Does this work with systemd timers or CI jobs?
Yes. Anything that can send an HTTP request at the end works: cron, systemd, Windows Task Scheduler, CI pipelines.
Your next successful job run can already be monitored.
Create a heartbeat, add the ping URL and define the interval.
Monitor for free