monero: check every five minutes again

The probes, the unit check and the public checks ran once a day with 26h
windows, justified as "a multi-week initial sync on a rotating disk". That
stopped being true: the node is synced, and a cold explorer page now renders
in 29s and a warm one in 0.2s - polling every 5 minutes is what keeps it warm.
A dead monerod could go unnoticed for a day.

Back to the standard 5m cadence and 11m heartbeat; the per-host
service_health override on monerod-box is gone.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

ansible/infra/401_service_monitoring.yml

@@ -99,9 +99,9 @@
         healthcheck_units: "{{ monitored_services }}"
         healthcheck_units_key_prefix: "services_{{ host_key }}"
         # Cadence and heartbeat window are ONE decision, and both are a property
-        # of the host - monerod-box runs a multi-week sync nobody needs polled
-        # every five minutes, so it declares a daily schedule in its host_vars
-        # and a matching window above. Everything else keeps 5min/11m.
+        # of the host: a host can set service_health_on_calendar and a matching
+        # service_health_heartbeat in its host_vars. None does today; everything
+        # runs 5min/11m. (monerod-box was daily during its initial sync.)
         #
         # An empty healthcheck_on_calendar means "use healthcheck_interval" -
         # see the timer template in roles/healthcheck.

ansible/infra/402_public_monitoring.yml

@@ -30,11 +30,8 @@
       - {sub: "{{ subdomains.memos }}",              host: vipy}
       - {sub: "{{ subdomains.mempool }}",            host: vipy}
       - {sub: "{{ subdomains.datum_gateway }}",      host: vipy}
-      # Daily rather than the 6h default - see the Monero note under
-      # public_sites. A record that has not moved in a year does not need
-      # four looks a day while the node behind it is mid-sync.
-      - {sub: "{{ subdomains.monero }}",             host: vipy, interval: '24h'}
-      - {sub: "{{ subdomains.monero_explorer }}",    host: vipy, interval: '24h'}
+      - {sub: "{{ subdomains.monero }}",             host: vipy}
+      - {sub: "{{ subdomains.monero_explorer }}",    host: vipy}
       - {sub: "{{ subdomains.music }}",              host: vipy}
       - {sub: "{{ subdomains.jar_lid_archive_staging }}", host: vipy}
 
@@ -58,16 +55,8 @@
       # 401 is CORRECT: monerod answers an unauthenticated request with an HTTP
       # Digest challenge. Asserting 200 here would go green precisely when
       # rpc-login broke and the node started serving the world for free.
-      #
-      # Both Monero sites are polled ONCE A DAY, not every 5 minutes. The node
-      # is a multi-week initial sync on a rotating disk and the explorer reads
-      # the same LMDB, so a hard poll measures the disk more than the service -
-      # and a wedged explorer turned that cadence into 83 Signal messages in
-      # six hours. `threshold` drops with it: 3 failures at 5m is 15 minutes of
-      # tolerance, but at 24h it would be THREE DAYS before anyone heard. A
-      # daily check has no room for a blip, so it alerts on the first one.
-      - {name: monero,      sub: "{{ subdomains.monero }}",             path: "/get_info", status: 401, interval: '24h', threshold: 1}
-      - {name: exmrplore,   sub: "{{ subdomains.monero_explorer }}",    path: "/",       status: 200, interval: '24h', threshold: 1}
+      - {name: monero,      sub: "{{ subdomains.monero }}",             path: "/get_info", status: 401}
+      - {name: exmrplore,   sub: "{{ subdomains.monero_explorer }}",    path: "/",       status: 200}
       # /app/, not "/": checked live, "/" answers 302 (Navidrome redirects to
       # the SPA) and only /app/ returns 200 with the real UI. 200 rather than
       # 401 because Navidrome has no basic auth in front of it - the Subsonic

ansible/infra/403_service_probe_registration.yml

@@ -45,15 +45,12 @@
       - {name: mempool-mariadb,  host: mempool_box_local}
       - {name: mempool-backend,  host: mempool_box_local}
       - {name: mempool-frontend, host: mempool_box_local}
-      # The two Monero probes push ONCE A DAY, not every 5 minutes, so they
-      # need a window wider than a day. 26h, not 24h: the window must exceed
-      # the push interval or a check that reports exactly on time races its own
-      # deadline and alerts on jitter. The timers are OnCalendar 05:00 and
-      # 05:30 with RandomizedDelaySec=900, so the true worst case is ~24h15m.
-      # Cadence lives in roles/{monero,xmrblocks}/defaults/main.yml; the two
-      # are one decision and must move together.
-      - {name: monerod,          host: monerod_box_local, heartbeat: '26h'}
-      - {name: xmrblocks,        host: monerod_box_local, heartbeat: '26h'}
+      # Every 5 minutes like the rest since 2026-10-17 (they were daily while
+      # the node synced on a rotating disk). Cadence lives in
+      # roles/{monero,xmrblocks}/defaults/main.yml; it and this window are one
+      # decision and must move together.
+      - {name: monerod,          host: monerod_box_local}
+      - {name: xmrblocks,        host: monerod_box_local}
       - {name: navidrome,        host: music_box_local}
       - {name: jar-lid-archive-staging, host: jar_lid_staging_local}