<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Adept Productions — AMP Watchdog dev notes</title><description>Development updates for AMP Watchdog, nothing else.</description><link>https://adeptproductions.dev/</link><item><title>Sleeping isn’t always healthy</title><link>https://adeptproductions.dev/dev-notes/2026-10-17-amp-watchdog-liveness/</link><guid isPermaLink="true">https://adeptproductions.dev/dev-notes/2026-10-17-amp-watchdog-liveness/</guid><description>AMP said the server was sleeping. The port was open. Nobody could join.

That exposed a blind spot in [AMP Watchdog](/apps/amp-watchdog/): asking the control panel whether a server is healthy only works if the panel has the full picture. AMP’s wake-on-connect listener had stopped responding, while its status still looked normal.

The watchdog now makes an actual Minecraft status request alongside the AMP check. An open connection alone doesn’t count—it needs a valid response. Two consecutive failures mark a configured watch offline and feed into the existing alert rules, reducing the chance of a brief handover triggering an alert.

Discord mentions stay reserved for offline alerts. Sleep transitions and recovery messages don’t need to ping everyone.

AMP Watchdog is now running on my production servers. The update passed 65 automated tests, including cases where a connection opens but the server never answers.

For now, it alerts me when something needs attention. Automatic recovery can come later.</description><pubDate>Sat, 17 Oct 2026 23:15:00 GMT</pubDate><category>update</category><category>amp-watchdog</category></item></channel></rss>