No monitoring checks for wal-e problems
Bug #1814523 reported by
Barry Price
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| PostgreSQL Charm |
Fix Released
|
High
|
Barry Price | ||
Bug Description
If the operator has configured wal-e to perform PITR backups, there should be a mechanism or mechanisms (e.g. Nagios checks, Prometheus metrics, etc) to inform/alert the operator in any case where the backup process is not working as expected.
This is particularly relevant to LP:1814484.
Related branches
~barryprice/postgresql-charm/+git/postgresql-charm:master
- Stuart Bishop (community): Approve
-
Diff: 315 lines (+235/-5)6 files modifiedconfig.yaml (+16/-4)
reactive/postgresql/nagios.py (+50/-1)
scripts/check_latest_ready_wal.py (+54/-0)
scripts/find_latest_ready_wal.py (+27/-0)
unit_tests/test_check_latest_ready_wal.py (+49/-0)
unit_tests/test_find_latest_ready_wal.py (+39/-0)
| description: | updated |
| description: | updated |
| Changed in postgresql-charm: | |
| status: | New → In Progress |
| importance: | Undecided → High |
| Changed in postgresql-charm: | |
| assignee: | nobody → Barry Price (barryprice) |
| Changed in postgresql-charm: | |
| status: | In Progress → Fix Committed |
| Changed in postgresql-charm: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
