Pulsewise

Heartbeat Monitoring

Know when your cron jobs stop beating.

Scheduled tasks fail silently. Backups stop running, queue workers crash, data syncs stall — and no one notices until the damage is done. Pulsewise listens for heartbeat pings from your jobs and alerts you the moment they stop arriving.

Start Free Trial
No credit card required
7-day free trial
Cancel anytime
The Problem

Silent failures are the most dangerous kind

Cron jobs don't fail loudly. When a backup script crashes, there's no error page. When a queue worker stops processing, emails just quietly stop sending. When a data sync breaks, reports start showing stale numbers — and nobody connects the dots until days later.

Traditional uptime monitoring can't help here. These aren't HTTP endpoints you can ping — they're internal processes that need to report in on their own schedule. Without heartbeat monitoring, you're flying blind on the tasks your business depends on most.

Heartbeat status

Database backup

Every 6 hours · Last: 2 hours ago

Healthy

Queue worker

Every 1 minute · Last: 45 seconds ago

Healthy

Invoice sync

Every 1 hour · Last: 3 hours ago

Late

Report generation

Daily at 6am · Last: 2 days ago

Down
The Solution

A unique URL for every job to ping

Pulsewise gives each heartbeat monitor a unique URL. Add a simple HTTP request to the end of your cron job, queue worker, or scheduled task. When the ping arrives on time, everything is healthy. When it doesn't, we alert you.

Configure the expected interval and a grace period for each heartbeat. A backup that runs every 6 hours gets a different tolerance than a queue worker that pings every minute. You define what "on time" means for each job.

Integration example

# Add to your cron job or script
$ your-backup-script.sh
$ curl -s https://pulse.pulsewise.app/h/abc123
# Or in Laravel scheduler
$schedule->command('backup:run')
->daily()
->thenPing('https://pulse.pulsewise.app/h/abc123');

What Pulsewise provides

  • Unique heartbeat URL for every monitored job
  • Configurable expected intervals (minutes, hours, or days)
  • Grace periods to account for normal timing variations
  • Instant alerts when a heartbeat is missed
  • Full history of every ping received
  • Works with cron jobs, queue workers, and any HTTP-capable script
  • Simple one-line integration with curl, wget, or framework schedulers

Start monitoring in minutes

Try us out with a free 7-day trial. No credit card required.

Need help? Get in touch at [email protected]