Adam Moussa a7536f0bd7 Fix daily flapping of backup-verification errors alarm (#23) ... The forgejo-backup-verification Lambda runs once per day, so its Errors metric has data for only one hour and is missing for the other ~23h. The errors alarm used TreatMissingData=BREACHING, which treated those 23h of missing data as a breach and flipped the alarm OK->ALARM every day around 11:01 UTC despite zero actual errors. Changes (alarm-only, no instance changes): - ErrorAlarm: TreatMissingData BREACHING -> NOT_BREACHING. No data now means "no errors = healthy" instead of a false breach. - Add forgejo-backup-verification-not-running: Invocations Sum over a 24h period, alarms when < 1 invocation. This is the real "the daily verification never ran" guard that the BREACHING setting was trying (incorrectly) to provide. Both alarms keep the existing action wiring (no SNS/OK actions), per the org convention of never notifying on recovery.		2026-06-05 14:34:45 -04:00
..
backup-verification.ts	Fix daily flapping of backup-verification errors alarm (#23)	2026-06-05 14:34:45 -04:00