Rippler docs
Command line

Commands

Every command, and what it does.

rippler exec

rippler exec <monitor> -- <command...>

Runs a command and reports it. This is what sync puts in your crontab.

rippler exec 7gM7Qy7 -- /usr/local/bin/backup.sh --full

It reports the run starting, then reports success or failure from the command's exit code, sending the measured duration and a run id with the closing ping.

Three properties matter if you are putting this in front of a real job:

  • The command's exit code becomes exec's exit code. Cron still sees what it would have seen.
  • stdout and stderr pass straight through. A wrapper that swallowed either would break the job it is meant to be watching, and hide it from your mail.
  • A monitoring outage cannot fail your job. Pings that do not go through are dropped, not raised.

rippler sync

rippler sync [--dry-run] [--yes] [--project <shortID>]

Reads your crontab, creates a monitor for every job that has none, and rewrites those lines to run under exec. See crontab handling for exactly what it will and will not touch.

FlagEffect
--dry-runPrint the plan and stop. Nothing is created or changed.
--yesSkip the confirmation. For scripts.
--projectPut new monitors in this project instead of the first one.

rippler list

Shows every monitor in your team with its status and schedule.

Nightly backup  7gM7Qy7  up    At 03:00 AM
poll.sh         jGDc_zz  down  Every 15 minutes

rippler projects

Lists your projects and their short ids — useful for sync --project.

rippler login

rippler login [--token <token>] [--url <api-url>]

Stores an API token after checking it works. See Install.

rippler version

On this page