personal_infra/ansible
counterweight f33f1a4b67
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>
2026-10-19 22:10:24 +02:00
..
group_vars ntfy-emergency-app: remove it 2026-10-19 22:10:22 +02:00
host_vars monero: check every five minutes again 2026-10-19 22:10:24 +02:00
infra monero: check every five minutes again 2026-10-19 22:10:24 +02:00
playbooks jar-lid-archive: a staging deployment on its own box 2026-10-03 23:56:30 +02:00
roles monero: check every five minutes again 2026-10-19 22:10:24 +02:00
services playbooks: stop re-runs overwriting live config 2026-10-19 22:10:23 +02:00
ansible.cfg now using password 2026-09-11 17:59:41 +02:00
inventory.ini rebuild: fold monitoring into spacey and prd-arbret into vipy 2026-10-19 22:10:22 +02:00
requirements.yml uptime-kuma: annotate config and drop the unused collection 2026-09-11 22:43:56 +02:00
site.yml ntfy-emergency-app: remove it 2026-10-19 22:10:22 +02:00