Comment on What sort of things do y'all monitor with Grafana / Beszel / etc.?
ultimaluz@lemmy.world 5 days ago
I’d add backup age and size, not just status, like alert if the newest dump is older than ~26h or smaller than 1MB, a job can say success and still leave you a useless file. and disk fill with a threshold, not only the graph. learned that one the hard way, a table on my vps was getting a row every minute with no cleanup and one day the disk hit 100% and postgres just died for like 40 min, obviously nobody was looking at the dashboard right then lol. now 80% warns and 90% sends me an email, and uptime kuma checks the cert expiry from outside. I guess the dashboard is nice to look at but the stuff that matters should ping you
glorp@lemmy.world 5 days ago
Size is a great idea, thanks. The problem with backup age is that Backrest doesn’t expose a metric for when the backup was attempted, so right now it’s just checking for failure status daily. That, of course, fails if backrest doesn’t attempt a backup for whatever reason. Chances of that happening, I don’t know, but I’ll have to look into implementing the metric (or label, I suppose) myself.
ultimaluz@lemmy.world 4 days ago
What I do for that is turn it around, instead of checking for a failure I alert on the absence of a success. backrest has hooks, so on snapshot success it pings a push monitor in uptime kuma (healthchecks.io works the same), and if no ping arrives in ~26h it alerts. That way it catches the backup that never ran, which is the one that scares me the most I guess
glorp@lemmy.world 20 hours ago
Oh, that’s really interesting! I couldn’t find a way to find absence of success given Backrest’s metrics alone, but using hooks for that seems to solve that problem well. Thanks!