Seiri guides
Heartbeat monitoring
Heartbeat monitoring answers one question: did the job call home? Your process pings Seiri on success. If the ping never arrives, you get alerted — before customers or finance notice.
Cron job monitoring
Heartbeat monitoring
Dead man's switch
Scheduled jobs
K8s CronJobs
Kube agent
Email heartbeats
Background jobs
What is heartbeat monitoring?
Unlike uptime monitoring (which polls a public URL), heartbeat monitoring is push-based. The workload proves it ran by checking in. Silence is the failure signal.
That catches hung jobs, skipped schedules, and “exit 0 but did nothing” failures that URL probes never see.
How Seiri implements it
- ·Create a webhook with a schedule + grace period
- ·Ping https://ping.seiri.app/ (or email @ping.seiri.app)
- ·Alert via Slack, email, Discord, Teams, or webhooks when a check-in is missed
- ·Optional: Kubernetes HealthChecks via seiri-kube-agent
Example
0 2 * * * /backup.sh && curl -fsS https://ping.seiri.app/NkdyngWn9z
FAQ
Is heartbeat monitoring the same as uptime monitoring?
No. Uptime tools ask “can we reach you?” Heartbeats ask “did you call home?”
Who needs heartbeat monitoring?
Anyone running cron, batch, ETL, digests, or queue workers where silence is dangerous.