Who watches the watchdog? The boring work behind a monitoring SaaS
Description and use
PulseWatch added external watchdog via Healthchecks.io, updated scheduler documentation, and established a real support channel, improving reliability and user trust.
Problem
PulseWatch’s monitoring system lacked self‑monitoring, clear scheduler guidance, and a real support channel, risking unnoticed failures and user confusion.
Outcome
PulseWatch now detects its own watchdog failures, provides clear scheduler guidance, and offers real support, increasing reliability and user trust.
Workflow
- 1. Instrument PulseWatch watchdog with Healthchecks.io start/success/failure signals. 2. Configure Healthchecks to alert on missed starts. 3. Publish documentation covering expected interval, grace, max‑runtime, and scheduler jitter. 4. Add live support link and domain email. 5. Test full support loop: send, receive, reply, confirm delivery.
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-21T11:45:36.729Z