summaryrefslogtreecommitdiff
path: root/flora/services/monit.nix (unfollow)
Commit message (Collapse)AuthorFilesLines
5 daysmonitoring: add cloud.infra4future.de via httpsstuebinm1-0/+4
7 daysmonitoring: check nobelium via httpsstuebinm1-2/+2
openssh starts to deny recurring connections that don't try to authenticate after a while, which seems to be what monit is doing for the ssh check.
11 daysmonitoring: check that nobelium is runningstuebinm1-0/+4
… might be good to also add a monit on nobelium itself, but in any case this isn't wrong either.
2024-04-07common/headless: basic monitoring on by defaultstuebinm1-32/+0
2024-03-11pkgs/scripts: monit->prometheus converterstuebinm1-0/+9
Not sure yet how much (if anything) I'll actually do with this, but it seemed like a fun idea to try and it's been way to long since I wrote anything in scheme. Entirely untested, as I don't actually have a prometheus running atm (apart from the one specifically for tracktrain on chaski).
2024-03-07monit: add stuff for infra4future.destuebinm1-1/+13
2024-03-04monit: extra catch-all check via systemctl is-system-runningstuebinm1-0/+3
2024-03-04monit: some kinda reasonable checksstuebinm1-4/+35
2024-02-29flora: monit via ntfy shstuebinm1-0/+32
so it turns out ntfy can run a little smtp server, which monit can send its alerts to, resulting in a halfway okayish monitoring setup. It doesn't even require mucking about with `sendmail'! Downside: this is still monit. Upside: from what I've heard, the other monitoring tools don't actually seem to be all that much better? Now I only have to come up with reasonable checks for the stuff I want to actually keep an eye on …