69
Looking for FOSS server monitoring UI (feddit.nl)
submitted 9 months ago by to c/selfhosted@lemmy.world
24 comments fedilink hide all child comments
 

Hey everyone,

I have an unraid server and over the years I've gathered quite a lot of tools, some of which are now exposed to the net.

I've been mostly checking on my server every once in a while to see if things are healthy, but I would like a more central version to look into the health of my network, any issues from docker logs, etc.

Anyone got a good ui for that? (preferably deployed through docker)

you are viewing a single comment's thread
view the rest of the comments
[–] 16 points 9 months ago (8 children)

I know these projects cockpit, netdata and grafana + prometheus.

  • permalink
  • fedilink
  • source
  • hideshow 8 child comments
    •
  • [–] 7 points 9 months ago* (7 children)

    Why Grafana + Prometheus? Why do they have to go together?

    Edit: I went back and reread... I think Prometheus is the data grabbing/monitor and Grafana is the polished UI dashboard???

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 7 points 9 months ago (6 children)

    Yes. Prometheus isn't standalone though, it requires agents on all target machines. The go-to is node exporter. It's really flexible though and there's agents for lots of different tools, you can monitor everything with it, but the initial setup isn't suuper easy.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 2 points 9 months ago (5 children)

    Someone opened my eyes recently to Yunohost which is a container manager essentially (my understanding) though is based on Debian for the newer versions not actual Docker.

    Anyway, I can install Prometheus as well as node explorer, but I think I would only need Prometheus. Node explorer sounds like if I hosted Prometheus on another box and wanted this host to talk to it.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 5 points 9 months ago* (last edited 9 months ago) (4 children)

    Prometheus is a metric scrapper, it just recollects metrics from either its own computer or another one. If you want to monitor something, you also need that something to publish metrics, so they can be scrapped by Prometheus.

    Thus if you want to monitor even just a single computer, you need node-exporter to publish the metrics, and Prometheus to gather them. Then you can use Grafana to create beautiful dashboards (or use community's), and even add alarms to it.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 1 point 9 months ago (3 children)

    Dang, that's a lot of seperate parts for 1 "simple" task smh. It's one of the reasons I've stayed away from all this Docker nonsense. I get it's FOSS and is a great alternative to a lot of paid garbage, but just seems like there could be an easier way... Nice to learn, tinker, etc, but if it breaks, then it seems more complicated to fix as each component is separate.

    I've just supported Window for so long and there's a second-nature to troubleshooting; but took years to get there, ya know? I'll check it out for sure, but I'm still going to look around myself

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 4 points 9 months ago* (1 child)

    Dang, that's a lot of seperate parts for 1 "simple" task

    Agree, but this setup (node-exporter + Prometheus + Grafana) allows for a lot of expansion and customization. I'm sure there are simpler tools that tell you your computer status, and it's up to you to see which fits more your use-case.

    but just seems like there could be an easier way

    I've felt that way before. But in this case of node-exporter and Prometheus, it's way simpler. You don't even need Docker, and the installation for both tools is basically a single line that you can copy and paste from their documentation.

    Configuring Prometheus to accept node-exporter is a bit harder I admit, but again you can simply copy and paste the documentation example. The whole process should take like ~10 minutes if you follow the documentation.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 9 months ago

    Not sure how that's related to docker. It's the prometheus setup which can be run natively just fine. Still needs an agent that actually retrieves info from the OS.

    Certainly there's "single executable" tools as well. I just don't know them.

  • permalink
  • fedilink
  • source
  • parent