uptime-kuma

Not quite as cheap as $5 but I've been running at Hetzner CAX31 for a couple of years now and I run the following services / apps. Actual Budget - https://github.com/actualbudget/actual AirTrail - https://github.com/johanohly/AirTrail Beszel - https://github.com/henrygd/beszel Coder - https://github.com/coder/coder Crowdsec - https://github.com/crowdsecurity/crowdsec Dawarich - https://github.com/Freika/dawarich Dozzle - https://github.com/amir20/dozzle Forgejo - https://codeberg.org/forgejo/forgejo Forgejo runner - https://code.forgejo.org/forgejo/runner Grafana - https://github.com/grafana/grafana Immich - https://github.com/immich-app/immich Karakeeo - https://github.com/karakeep-app/karakeep KitchenOwl - https://github.com/tombursch/kitchen owl Loki - https://github.com/grafana/loki Matrix - Tuwunel (https://github.com/matrix-construc

What I did is make the scripts ping uptime kuma https://github.com/louislam/uptime-kuma This has two advantages. First, if cron jobs are not running at all for some reason, the timeout will notify you. Second, you can also manually trigger error conditions by pushing to uptime kuma with an error message, exactly the same as if you used cron email notifications. If the uptime kuma endpoint is pinged with s higher frequency than the timeout you configured it to, then no alerts are fired.

> You need external monitoring of certificate validity. Plug for Uptime Kuma, they support notifications ahead of expiry: https://github.com/louislam/uptime-kuma Kind of cool to have an uptime monitoring tool that also had an option like that, two birds one stone and all that. Not affiliated with them, FOSS project.

> Powered by Uptime Kuma Uptime Kuma is really nice: https://github.com/louislam/uptime-kuma Supports all sorts of alerts and can even tell you if it ever looks like your TLS certs will soon expire (if any automation is broken, or you use commercial certs with manual rotation).

Uptime Kuma is FOSS, not sure if it is missing any features you might be expecting. Very easy to set up as well. https://github.com/louislam/uptime-kuma

Uptime Kuma already has some automatically generated badges[1], but not for specific events. Your could manually built your own custom ones based on the same framework[2] though. [1] https://github.com/louislam/uptime-kuma/wiki/Badge [2] https://shields.io/

Can recommend Uptime Kuma for this purpose: https://github.com/louislam/uptime-kuma

Lol. I opened that link and was like "hmmm, that UI looks familiar". I'm pretty sure that's just a frontend for Uptime Kuma https://github.com/louislam/uptime-kuma

It seems to be an instance of Uptime Kuma, which is a pretty great OSS for uptime monitoring and Dashboarding. https://github.com/louislam/uptime-kuma

I use uptime-kuma[1] with notifications sent out through the included Apprise integration[2] 1. https://github.com/louislam/uptime-kuma 2. https://github.com/caronc/apprise

Not that I think that an API is fundamental to a monitoring tool, but it happens to have one: https://github.com/louislam/uptime-kuma/wiki/API-Documentati...

Uptime Kuma (https://github.com/louislam/uptime-kuma). With email notifications. So much simpler, and free.

Your understanding is correct, unfortunately. Not only that, the developers are also reluctant to make 127.0.0.1:####:#### the default in their READMEs and docker-compose.yml files because UsEr cOnVeNiEnCe, e.g. https://github.com/louislam/uptime-kuma/pull/3002 closed WONTFIX

I switched to Kuma recently, but it's not all roses either. Their Docker image is based on Debian 10 with Go 1.19 and they don't feel the need to update because "OS level bugs are seldomely exploitable" https://github.com/louislam/uptime-kuma/issues/4885 So host it on a separate machine and don't put any secrets in there