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>
This commit is contained in:
parent
532974634e
commit
f33f1a4b67
8 changed files with 36 additions and 73 deletions
|
|
@ -104,15 +104,17 @@ healthcheck_push_url: ""
|
|||
# is set: Gatus rejects an unauthenticated push with 401.
|
||||
healthcheck_push_token: ""
|
||||
|
||||
# WHEN TO CHECK. Daily, at a fixed hour, rather than an OnUnitActiveSec
|
||||
# interval that drifts with every restart.
|
||||
# WHEN TO CHECK. Every 5 minutes, on the calendar rather than OnUnitActiveSec so
|
||||
# the cadence does not drift with every restart. (It was daily while the node
|
||||
# did its initial sync on a rotating disk; since 2026-10-03 the chain is on NVMe
|
||||
# and fully synced, and get_info answers in well under a second.)
|
||||
#
|
||||
# Prefixed because the generic `healthcheck` role owns the unprefixed
|
||||
# healthcheck_on_calendar; an unprefixed default here would shadow it for any
|
||||
# play that includes both.
|
||||
#
|
||||
# Paired with the 26h Gatus heartbeat in
|
||||
# Paired with the standard 11m Gatus heartbeat in
|
||||
# infra/403_service_probe_registration.yml. Change one and you must change the
|
||||
# other: the window has to stay above the interval or the check alerts on its
|
||||
# own jitter.
|
||||
monero_healthcheck_on_calendar: "*-*-* 05:00:00"
|
||||
monero_healthcheck_on_calendar: "*:0/5"
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue