Who watches the watchdog? The boring work behind a monitoring SaaS
Description and use
PulseWatch added external watchdog via Healthchecks.io, updated documentation on intervals and timeouts, and created a real support channel, improving reliability and user trust.
Problem
PulseWatch’s monitoring system lacked self‑monitoring, clear configuration guidance, and a real support channel, risking silent failures and user confusion.
Outcome
PulseWatch now detects its own watchdog failures, provides clear configuration guidance, and offers a verified support channel, reducing silent failures and improving user trust.
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 documentation to explain expected interval, grace, max‑runtime, and scheduler jitter. 4. Add a live support link and test full email loop (send, receive, reply, confirm).
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.
I tested the complete loop rather than stopping once outgoing mail worked: 1. Send from the PulseWatch address 2. Receive it in an external inbox 3. Reply to it 4. Confirm the reply arrives in the correct PulseWatch inbox
- Record date: 2026-09-05T18:59:55.076Z