One line. The one you already have.
Add a curl to the end of it. That is the integration.
0 3 * * * /usr/local/bin/backup.sh && curl -fsS -m 10 -o /dev/null https://api.rippler.io/ping/7gM7Qy7/Know the moment a cron job stops running.
Your job pings a URL when it finishes. Miss one and we tell you.
10 monitors free. No credit card.
Nightly backup
UpAt 03:00 AM · in 6 hours
90 days agoToday
Ninety days, one bar a day, worst status wins. An example — not anyone’s real uptime.
Four words for what happened
UpRunningLateDown
Late is its own state. A job that is one minute over is not an outage yet, and we do not wake you for it.
It knows when to expect you
Every cron expression is read back in English with its next three runs, so a typo is caught at the form — not by an alert that quietly never fires.
Alerts that shut up
Set a tolerance and a job that fails once and fixes itself stays quiet. Email, or straight into Discord.
Or hand it the whole crontab
rippler sync wires up every job in it, shows you the plan first, and does nothing the second time you run it.
$ rippler sync --dry-run
create 0 3 * * * backup.sh
create @daily cleanup.sh
keep */5 * * * * already monitored
skip @reboot no schedule to expect pings againstIt times each run
Wrap the job in
/start and /end. Overlapping runs still measure correctly — each one carries its own id.Two plans. That is the whole price list.
Indie
Free
10 monitors. Everything, for ten jobs.
Business
$25 a month
100 monitors. A hundred jobs, one flat price.
Both include unlimited people on the team, every alert channel, the API and the CLI. The plans differ only in how many jobs you watch.