23

I'm curious what people are using to monitor their backups? I have Borg running on a cronjob, but checking logs periodically is getting tedious, so I'd like to automate that if possible

you are viewing a single comment's thread
view the rest of the comments
[-] TechnicallyColors@lemm.ee 14 points 4 months ago* (last edited 4 months ago)

I recommend a dead man's switch like Healthchecks.io, which can be selfhosted for free. Whenever you have something that's regularly occurring, add an extra callout to your unique Healthchecks callout UUID as part of the automation, and Healthchecks will send you a notification if something misses its callout schedule. You can also attach whatever data (e.g. a log) to the callout so you can look back through the run history. IIRC Borg will give you a non-zero return code if it detects problems, so you can send e.g. https://hc-ping.com/your-uuid-here/$? and a non-zero code will signal a notification as well (more examples here).

Also, Borgmatic is really easy to use for managing Borg repos. There's a lot of configuration options (including Healthchecks.io integration) but you can delete like 90% of it for normal usecases.

[-] tritonium@midwest.social 0 points 4 months ago* (last edited 4 months ago)

I use healthchecks for all my scripts and making sure my docker containers and services are up. If anything goes down or errors then I get sent a telegram message immediately.

this post was submitted on 08 Jul 2024
23 points (92.6% liked)

Selfhosted

40198 readers
453 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS