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?

all 7 comments

sorted by: hot top controversial new old
[–] 7 points 1 year 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.

  • source
  • hideshow 4 child comments
  • [–] 5 points 1 year ago (1 child)

    +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.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 1 year ago
    [–] 2 points 1 year ago

    I am currently setting up munin on my servers.

    I like it so far - it's old-school, lightweight and straightforward.

  • source