counterweight/personal_infra
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

monero: check every five minutes again

Browse source 
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>
This commit is contained in:
counterweight 2026-10-19 22:10:24 +02:00
parent 532974634e
commit f33f1a4b67
Signed by: counterweight
GPG key ID: 883EDBAA726BD96C
8 changed files with 36 additions and 73 deletions
Download patch file Download diff file Expand all files Collapse all files

11
ansible/roles/xmrblocks/defaults/main.yml
View file

@ -74,8 +74,9 @@ healthcheck_push_url: ""
# is set: Gatus rejects an unauthenticated push with 401.
healthcheck_push_token: ""
# WHEN TO CHECK. Daily, 30 minutes after monerod's own check so the two do not
# contend for the same cold LMDB pages. See roles/monero/defaults for why the
# name is prefixed and why this is paired with the 26h heartbeat in
# infra/403_service_probe_registration.yml.
xmrblocks_healthcheck_on_calendar: "*-*-* 05:30:00"
# WHEN TO CHECK. Every 5 minutes, offset 2 minutes from monerod's own check so
# the two do not land together. On NVMe a cold page render measured 29s and a
# warm one 0.2s (2026-10-17); a 5-minute poll is what keeps it warm. See
# roles/monero/defaults for why the name is prefixed and why this is paired
# with the 11m heartbeat in infra/403_service_probe_registration.yml.
xmrblocks_healthcheck_on_calendar: "*:2/5"