| Commit message (Collapse) | Author | Files | Lines | ||
|---|---|---|---|---|---|
| 2024-04-07 | common/headless: basic monitoring on by default | stuebinm | 1 | -32/+0 | |
| 2024-03-11 | pkgs/scripts: monit->prometheus converter | stuebinm | 1 | -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-07 | monit: add stuff for infra4future.de | stuebinm | 1 | -1/+13 | |
| 2024-03-04 | monit: extra catch-all check via systemctl is-system-running | stuebinm | 1 | -0/+3 | |
| 2024-03-04 | monit: some kinda reasonable checks | stuebinm | 1 | -4/+35 | |
| 2024-02-29 | flora: monit via ntfy sh | stuebinm | 1 | -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 … | |||||
 |
index : nixfiles | |
| my nixfiles |
| summaryrefslogtreecommitdiff |