I use https://github.com/louislam/uptime-kuma
I'm not sure about ansible automations, but for uptime monitoring, it's really simple and effective.
this post was submitted on 16 Oct 2024
32 points (92.1% liked)
Selfhosted
40329 readers
419 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
Just a heads-up, until v2 is released, it does not scale. I used it to monitor around 40 services. It's too much. So if you have a lot of things to monitor for uptime you might need to either split in several uptime-kuma services, or reduce the frequency
First I'm hearing of a V2, are there any threads on github or posts detailing this so I know what to look for?
Edit: just kidding, found the issue and milestone on github now
Monitor Ansible automations? I'm not sure why you'd need timeseries capable metrics and graphing for that. If you just wanted a prebuilt solution, look at Chronograf.
I'd go for netdata, if you just want to monitor the health of your entire Linux server, and Uptime Kuma for checking individual services. You can also set it up, so that you receive a notification if a service goes down, e.g. over ntfy or Pushover. See the documentation for Uptime Kuma push notifications https://github.com/louislam/uptime-kuma/wiki/Notification-Methods
I switched from Grafana to CheckMK I love how we can create custom scripts and agents are so easy to install.
You could have a look at munin. It's incredibly simple but effective. Quite easy to write your own plugins for if you're missing some data. http://munin-monitoring.org/
It sounds strange maybe,but I found Zabbix way easier for these scenarios. For more advanced deployments it is different,but for what you describe it is really easy
What about switching to Prometheus for metrics and snagging some premade dashboards in Grafana? Since it's pull-based, up is a freebie, especially if you expose the node_exporter via your reverse proxy.
It is too complicated for me. I am wanting simplicity and quite customization
Very understandable and valid. I find that Prometheus' query language makes a lot of sense to me, so, I like it. Have you tried Cacti or Nagios?