Comment on Looking for FOSS server monitoring UI

• tofu@lemmy.nocturnal.garden ⁨22⁩ ⁨hours⁩ ago

  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.

  source

  • mrnobody@reddthat.com ⁨22⁩ ⁨hours⁩ ago

    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.

    source

    • Danitos@reddthat.com ⁨22⁩ ⁨hours⁩ ago

      Prometheus is a metric scrapper, it just recollects metrics from either it’s 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.

      source

      • mrnobody@reddthat.com ⁨21⁩ ⁨hours⁩ ago

        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

        source

        • -> View More Comments