Who watches the watchdog? The boring work behind a monitoring SaaS
Description and use
PulseWatch added an external watchdog via Healthchecks.io, updated documentation on interval settings, and introduced a support channel, improving reliability and user trust.
Problem
PulseWatch’s monitoring system risked silent failures: its own watchdog could stop, leaving users unaware of missing alerts, and users struggled to configure grace periods and support channels.
Outcome
PulseWatch now reliably detects its own watchdog failures, provides clear configuration guidance to avoid false alerts, and offers a functional priority support channel, increasing trust and dependability.
Workflow
- 1. Instrument PulseWatch watchdog to send start, success, and failure signals to Healthchecks.io. 2. Configure Healthchecks.io to alert if the watchdog never starts. 3. Update PulseWatch documentation with: - 60‑second getting‑started guide - /start → /success or /fail lifecycle - Python and Bash/curl integration examples - Guidance on expected interval, grace, max‑runtime, and scheduler jitter - Definitions of MISSING, STUCK, FAILED, flapping, NEVER_RUN 4. Add a live support link and domain email ([email protected]) for priority support. 5. Test the support loop: send, receive, reply, and confirm reply arrives correctly.
Evidence
I’ve now instrumented the watchdog using Healthchecks.io, which runs outside the PulseWatch infrastructure.
The page is linked from the main navigation and footer, and the public route now has its own focused test.
There is now a live support link and a working domain email address at [email protected].
- Record date: 2026-09-15T12:32:55.971Z