DumbMonit

ИнтеграцииПроверки и heartbeat

Heartbeat (push)

Your cron job or backup script calls DumbMonit; when it goes quiet, you are told.

Документация

Описания на английском, как в самом продукте. Подписи на странице — на вашем языке.

Что проверяет DumbMonit

The silent failure nobody notices: the nightly backup that stopped running after an update, the certificate renewal cron that lost its permissions, the Home Assistant automation that broke on a rename. Nothing complains, and you find out the day you need the backup. A heartbeat monitor (also called a *dead man's switch*, or a *push* monitor in Uptime Kuma) turns the logic around: DumbMonit contacts nothing. The job calls a secret URL each time it runs, and it is the absence of a call that raises the alert.

Типичное применение. Cron job, backup script, automation that must call in

Примеры

  • Nightly backup script
  • Cron job
  • Home Assistant automation
  • Certificate renewal
  • Database dump

Как подключается

Учётная запись не нужна.

Сетевые порты, которые нужно открыть

  • 8080/TCPHeartbeat call (default port, 443 behind a proxy)
Шаги настройки: Make the job call in
  1. In the address, write a short label for the job, unique among your heartbeats: "nightly-backup".

  2. Set the expected interval to the job's schedule ("24h" for a nightly job), or give a cron expression and a time zone, then save the monitor.

  3. Copy the URL shown on the monitor page and call it at the end of the job.

    curl -fsS -m 10 --retry 3 https://monit.example.com/api/push/<token>
  4. To time the job, call .../start before it, then .../success or .../fail after it, with its output as the request body. Send an exit code as ?exit_code=2 or as .../2.

  5. To report a failure at once, append ?status=down&msg=... to the URL.

Обратите внимание. Call the URL at the end of the job, after the part that matters: a call at the top would report a success even when the job fails.