Find out when a scheduled job quietly stops
For developers whose nightly jobs fail without a sound.
The problem
- A cron job dies, and nobody notices for a week.
- Logs only help if someone reads them.
- Site checks can't see jobs that run in the background.
How vizsu helps
One ping per run
Your job calls a unique URL when it finishes. If the ping doesn't arrive on time, we alert you.
Same alerts as everything else
Email, SMS, web push, Slack, Discord, Telegram or webhook.
Escalation and incidents
A missed heartbeat opens an incident and pages people until someone acks.
Built for code
Use the API with your API key and webhooks to fit Uptime into your own tools.
How it works
- Create a heartbeat. Tell us how often the job should run.
- Add the ping. Call the URL at the end of your job, for example with
your-job.sh && curl -fsS <your heartbeat URL>. - Get alerted. If a run is missed, we tell you.
Said plainly
We're new. Uptime is a young product, with no customer logos yet. Heartbeats work today with any job that can make an HTTP request.
Questions
What can send a heartbeat?+
Anything that can make an HTTP request: cron, a script, a queue worker.
What happens when a ping is late?+
An incident opens and your alert channels are notified.
Is there an API?+
Yes. Create an API key in Uptime and use it from your scripts.
How do I get help?+
Write to support@vizsu.com.
Related
Guide: how to monitor cron jobs · Site-down alerts · Developers · Plans and prices · All solutions