Open ben-ballot opened 11 months ago
Dear @darkalia thank you for the improvements request.
At the moment all the failed backups are marked the special prefix: "Backup failed" and all logs are forwarded to Loki where you can configure the Alert rule using the prefix.
It is an insetting idea to expose the last backup id as a metric, but today there is no easy way to implement it. Contact @7annaba3l to have it scheduled. Tnx!
Wouldn't a successful backup create an entry in the juju debug-log which would be relatively easy to inspect via Loki?
For instance, looking at the juju logs from a unit we're running in production I see:
2023-11-21 00:00:36 INFO unit.postgresql/0.juju-log server.go:325 Backup succeeded: with backup-id 2023-11-21T00:00:02Z
Just for the history: both successful and failed backup will make a trace in debug-log with INFO level (and available on Loki COS).
The idea to show backup metrics is great. We need Prometherus pgbackrest exporter first. I will keep the issue open.
Steps to reproduce
Expected behavior
Have a scrape-able metric for:
Actual behavior
Versions
Operating system: Ubuntu 18.04.6 LTS
Juju CLI: 2.9.42-ubuntu-amd64
Juju agent: 2.9.44
Charm revision: latest/stable