summaryrefslogtreecommitdiff
path: root/flora/services/monit.nix (follow)
Commit message (Collapse)AuthorAgeFilesLines
* monitoring: add cloud.infra4future.de via httpsstuebinm2024-07-041-0/+4
|
* monitoring: check nobelium via httpsstuebinm2024-07-011-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.
* monitoring: check that nobelium is runningstuebinm2024-06-271-0/+4
| | | | | … might be good to also add a monit on nobelium itself, but in any case this isn't wrong either.
* common/headless: basic monitoring on by defaultstuebinm2024-04-071-32/+0
|
* pkgs/scripts: monit->prometheus converterstuebinm2024-03-111-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).
* monit: add stuff for infra4future.destuebinm2024-03-071-1/+13
|
* monit: extra catch-all check via systemctl is-system-runningstuebinm2024-03-041-0/+3
|
* monit: some kinda reasonable checksstuebinm2024-03-041-4/+35
|
* flora: monit via ntfy shstuebinm2024-02-291-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 …