Self-hosting

3502 readers

1 users here now

Hosting your own services. Preferably at home and on low-power or shared hardware.

Also check out:

founded 3 years ago

MODERATORS

poVoq@slrpnk.net

sam_uk@slrpnk.net

[Recommendation request] Simple monitoring? (slrpnk.net)

submitted 3 days ago* (last edited 3 days ago) by BillyCrystalMeth@slrpnk.net to c/selfhosting@slrpnk.net

9 comments fedilink hide all child comments

I have a relative small home server running an *Arr stack and some other stuff. So basically just a handful of containers. I am looking for a simple monitoring setup with a web dashboard that I can access on my local network.

At work we use a big Grafana stack for monitoring, but that would be pretty overkill for my case. So do you guys have any tips for a simple monitoring setup?

you are viewing a single comment's thread
view the rest of the comments

[–] qaz@lemmy.world 7 points 3 days ago* (last edited 3 days ago) (4 children)

You can use Uptime Kuma. It's just 1 container with an SQLite database. It shows outages, uptime, and can sent notifications about service status.

[–] thirdBreakfast@lemmy.world 4 points 2 days ago

+1 for Uptime Kuma. I use it in conjunction with a tiny Go endpoint that exposes memory, disk and cpu. And, like @iii I use ntfy for notifications. I went down the Grafana/Influx etc route - and had a heap of fun making a dashboard, but then never looked at it. With my two Kuma instances (one on a VPS and one in my homelab) in browser tabs, and ntfy for notifications on my watch, I feel confidently across the regular things that can go wrong.

load more comments (3 replies)