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?

  • qaz@lemmy.world
    link
    fedilink
    English
    arrow-up
    7
    ·
    edit-2
    4 days ago

    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
      link
      fedilink
      English
      arrow-up
      4
      ·
      4 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.

    • iii@mander.xyz
      link
      fedilink
      English
      arrow-up
      4
      ·
      4 days ago

      I also wanted to recommend uptime kuma. Love it’s versatility. I combine it with ntfy.sh for near real time notifications.

      • qaz@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        4 days ago

        That also looks like a really interesting option, might try that myself