Alert on periodic jobs without recent successful exit #195

Merged
fabianhauser merged 3 commits from backup-job-success into main 2026-10-07 18:36:17 +00:00
Owner

Alternative to #186, for #178: alerts when a borg or postgres backup service hasn't exited successfully within 30h, based on systemd's own exit state.

  • After deploy, systemd_job_success is reported for every borg/postgres backup unit on all hosts
  • PeriodicJobNotSucceeded shows up in Grafana alerting and isn't firing
  • Remove the manual Grafana backup alerts from #178
  • Close #186
Alternative to #186, for #178: alerts when a borg or postgres backup service hasn't exited successfully within 30h, based on systemd's own exit state. - [ ] After deploy, `systemd_job_success` is reported for every borg/postgres backup unit on all hosts - [ ] `PeriodicJobNotSucceeded` shows up in Grafana alerting and isn't firing - [ ] Remove the manual Grafana backup alerts from #178 - [ ] Close #186
Alert on periodic jobs without recent successful exit
All checks were successful
CI / build (push) Successful in 5m1s
CI / deploy (docs-ops.qo.is) (push) Has been skipped
CI / deploy (system-physical) (push) Has been skipped
CI / deploy (system-vm) (push) Has been skipped
CI / deploy-ci (push) Has been skipped
1acd2d007b
Move periodic job alert rule to alertmanager module
All checks were successful
CI / build (push) Successful in 4m51s
CI / deploy (docs-ops.qo.is) (push) Has been skipped
CI / deploy (system-physical) (push) Has been skipped
CI / deploy (system-vm) (push) Has been skipped
CI / deploy-ci (push) Has been skipped
919017b784
fabianhauser deleted branch backup-job-success 2026-10-07 18:36:17 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
qo.is/infrastructure!195
No description provided.