this post was submitted on 07 Feb 2026
55 points (100.0% liked)

Selfhosted

56133 readers
954 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

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
[–] Danitos@reddthat.com 5 points 16 hours ago (1 children)

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.

[–] mrnobody@reddthat.com 2 points 16 hours ago (2 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

[–] Danitos@reddthat.com 4 points 16 hours ago* (last edited 16 hours ago) (1 children)

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.

[–] mrnobody@reddthat.com 1 points 13 hours ago

Sweet, thank you

[–] tofu@lemmy.nocturnal.garden 1 points 15 hours 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.