InfoFounding Members35 lifetime licenses available — view the offer > https://uptriva.com/foundingInfoMCP launch announcementConnect Claude, Cursor or any MCP client with your API token — let an agent create monitors, manage incidents and configure alerts. Read the docs → https://uptriva.com/docs/api/mcp
All check types
Apps & Workloads

Heartbeat / Cron Monitoring

Heartbeat monitoring inverts the model: instead of probing your service, your cron jobs and batch tasks ping a unique endpoint on a schedule. Silence past the deadline means the job died — or never ran.

The check for jobs that must call in — or something is wrong

What it checks

  • Expected ping intervals for cron jobs and batch tasks
  • Missed or late check-ins
  • Grace-period violations before alerting

Set it up

  1. 1Create a heartbeat monitor and copy its unique ping URL
  2. 2Add a curl to the end of your cron job or script
  3. 3Set the expected interval and grace window

FAQ

What is the difference between heartbeat and pull checks?

Probes ask 'does it respond'; heartbeats ask 'did it report in'. Backups, ETL and scheduled tasks have no port to probe — push is the only model that works.

Related check types

Internal Agent MonitoringSee what external probes physically cannotAPI MonitoringEndpoints that answer are not endpoints that workGame Server MonitoringPlayers see 'server offline' before your dashboard does — unless you watch the query port

Start monitoring in minutes

External probes plus internal agents, escalation chains and status pages — free tier, no card required.

Start free Read the docs