How to add cron job monitoring without changing your infrastructure

How to add cron job monitoring without changing your infrastructure

Crontify utilizes a push-based dead man’s switch model to monitor scheduled tasks. This system requires only three HTTP POST calls—start, success, and fail—to track job health without infrastructure changes.

Why This Matters

Traditional monitoring advice often mandates complex logging stacks and sidecar processes, which create significant setup overhead for solo developers and fast-moving startups. This push-based model provides a technical alternative that allows jobs to report status directly over HTTP, preventing production tasks from running unmonitored for months due to infrastructure complexity.

Key Insights

• The dead man’s switch model is push-based, meaning the monitored job announces its own health via HTTP rather than a monitoring system pulling status.
• Crontify (2026) parses cron expressions to detect missed runs caused by server reboots or deleted crontabs that traditional pull-based logging would miss.
• Hung job detection identifies deadlocks and infinite loops by alerting when a success ping fails to follow a start ping within a maximum duration threshold.
• The @crontify/sdk provides a wrap() function for Node.js that automatically handles start, success, and failure pings around existing job functions.
• Failure context including error stacks up to 10,000 characters can be attached to fail pings to deliver immediate debugging info to Slack or email.

Working Examples

Node.js integration using the SDK wrap method

import { CrontifyMonitor } from '@crontify/sdk'; const monitor = new CrontifyMonitor({ apiKey: process.env.CRONTIFY_API_KEY!, monitorId: 'your-monitor-id' }); await monitor.wrap(async () => { await yourExistingJobFunction(); });

Shell script implementation with curl

#!/bin/bash
set -e
MONITOR_ID="your-monitor-id"
API_KEY="${CRONTIFY_API_KEY}"
BASE_URL="https://api.crontify.com/api/v1/ping"
ping() {
curl -fsS -X POST "${BASE_URL}/${MONITOR_ID}/${1}" -H "X-API-Key: ${API_KEY}" > /dev/null 2>&1 || true
}
ping start
/usr/local/bin/your-backup-script.sh
ping success

Python implementation using the requests library

import os
import requests
def ping(event: str, monitor_id: str):
  try:
    requests.post(f"https://api.crontify.com/api/v1/ping/{monitor_id}/{event}", headers={"X-API-Key": os.environ["CRONTIFY_API_KEY"]}, timeout=5)
  except Exception: pass
monitor_id = "your-monitor-id"
ping("start", monitor_id)
try:
  your_existing_job()
  ping("success", monitor_id)
except Exception as e:
  ping("fail", monitor_id)
  raise

Practical Applications

• Use case: A developer running database backups on a VPS uses curl pings to ensure they are notified if the cron daemon itself fails. Pitfall: Failing to use ’|| true’ or try-except blocks in pings, which can cause the monitoring call to kill the actual job if the network is down.
• Use case: Fast-moving startups integrate the Crontify Node.js SDK to add monitoring to serverless functions in minutes without configuring log forwarders. Pitfall: Relying on pull-based monitoring for short-lived tasks, which may complete or fail between polling intervals.

References:

• https://dev.to/vincentabolarin/how-to-add-cron-job-monitoring-without-changing-your-infrastructure-khi