Rippler
Monitor scheduled jobs and websites, and get alerted when a run is late or fails or a site goes down.
Rippler watches jobs that run on a schedule, and websites. Your job calls a URL when it runs; a website Rippler requests itself. If the call does not arrive when expected, or the site stops answering, you get an alert.
Getting started
Create a monitor, add its ping URL and test your first alert.
Website monitors
Check a URL on an interval, and learn what counts as down.
Concepts
Understand statuses, schedules, grace periods, runs and alert thresholds.
Command line
Create monitors for an existing crontab without editing every job by hand.
HTTP API
Create monitors, inspect their status and report runs from your own tooling.
How monitoring works
A monitor expects a ping on a schedule. Three things can happen:
- The ping arrives on time. The monitor stays up, and nothing happens.
- The ping is late. The monitor enters its grace period. Nothing happens yet. Grace absorbs the normal variation in when a job finishes.
- Grace runs out, or the job reports a failure. The monitor goes down, and once it has failed as many times in a row as you allow, an alert goes out.
A job that fails occasionally and fixes itself on the next run does not have to alert. See failure tolerance.
Fix a missing ping
If a job runs but never shows up in Rippler, the cause is usually one of a few things, most of them outside Rippler. Troubleshooting covers them.