{
  "id": 9274355,
  "title": "Healthchecks: Monitor Cron Jobs & Backups (Dead Man's Switch)",
  "url": "https://urgent.news/2026/09/23/healthchecks-monitor-cron-jobs-backups-dead-mans-switch",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-23T04:56:11.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/serverkueche/healthchecks-monitor-cron-jobs-backups-dead-mans-switch-2oo1"
  },
  "original_language": "en",
  "account": "The article explains how to monitor recurring jobs, such as backups and database dumps, using Healthchecks, a self-hosted service that functions as a \"dead man's switch\". A key distinction between classic monitoring and Healthchecks is that Healthchecks monitors the job checking in with the server, rather than the server responding to requests. If a job fails to check in within a specified timeframe, Healthchecks raises an alert, notifying you of the issue before it becomes a problem.\n\nThe article outlines a step-by-step process to set up Healthchecks. The prerequisites include a server with Traefik running and Docker Compose installed, as well as a subdomain pointing to the server. Users should also create a Compose file that runs Healthchecks with SQLite, specifying a unique SECRET_KEY and allowed subdomain (YOUR_DOMAIN). The compose file includes Traefik labels for routing and setting up TLS encryption.\n\nAfter starting the Healthchecks service with Docker Compose, users access the application via their domain and create an account through the createsuperuser command. Once logged in, users create a project and a first check, specifying the expected interval between runs (period) and how long Healthchecks should wait before alerting (grace time). Healthchecks assigns a unique ping URL to each check, which the job must call after successful completion.\n\nTo implement this monitoring system, users modify their scripts to call the Healthchecks ping URL after the job completes successfully, including the check's UUID and the job's exit code. This ensures that any failures or delays are immediately detected and alert users to potential issues through Healthchecks.",
  "summary": "The most dangerous failures are the silent ones: the nightly backup hasn't run for three weeks – and no one notices until the data is actually needed. Uptime Kuma tells you when a service is up . Healthchecks tells you when a job didn't run . That difference is what saves data. What are we building? A self-hosted Healthchecks server (v4.4) behind Traefik that works as a dead man's switch : every…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}