Add prometheus metrics about restic #82

New Issue

2026-03-13T19:28:10Z

p4u1 commented

2026-03-13 19:28:10 +00:00

Problem:
Using Prometheus to track start and finish in the cronjob does not work reliable, since it depends on the backup taking longer than than the Prometheus scrape interval

Solution:
Use metrics about restic instead with something like:
https://github.com/ngosang/restic-exporter

Problem: Using Prometheus to track start and finish in the cronjob does not work reliable, since it depends on the backup taking longer than than the Prometheus scrape interval Solution: Use metrics about restic instead with something like: https://github.com/ngosang/restic-exporter

p4u1 changed title from ~~Prove prometheus metrics about restic~~ to Add prometheus metrics about restic

2026-03-14 06:46:59 +00:00

stevensting self-assigned this 2026-03-16 09:53:26 +00:00

stevensting referenced this issue

2026-03-18 22:00:42 +00:00

feat: add restic-exporter as metrics endpoint #84

fauno commented

2026-08-19 16:08:38 +00:00

now that monitoring-ng port to alloy is working it'd be good to add this!

👍 1

moritz commented

2026-08-31 17:59:07 +00:00

As stated here #84 (comment) I think it's not a good idea to expose any public facing ports in the backup bot. I also don't understand why it's necessary. monitoring-ng is able to read the docker logs of the backup bot. Isn't this enough?

As stated here https://git.coopcloud.tech/coop-cloud/backup-bot-two/pulls/84#issuecomment-32244 I think it's not a good idea to expose any public facing ports in the backup bot. I also don't understand why it's necessary. monitoring-ng is able to read the docker logs of the backup bot. Isn't this enough?

Sign in to join this conversation.

3 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/backup-bot-two#82