Selfhosted

39488 readers

251 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

-1

Any recommendations for monitoring my servers? (lemmy.world)

submitted 9 months ago by Aux@lemmy.world to c/selfhosted@lemmy.world

3 comments fedilink hide all child comments

Hi, I have a bunch of Raspberry Pies hosting all kinds of stuff and I want to have a monitoring solution for all of that. What would be your recommendations?

My goal is to be able to have an overview of CPU load, network load, CPU temp and to see what's going on inside docker containers as I have everything dockerized. I'd like the solution to be open source. I want the solution to be web browser accessible and have nice load graphs with history. I don't want to spend too much time setting it up.

All my Pies are running RaspberryOS, which is Debian based.

top 3 comments

sorted by: hot top controversial new old

[–] rettet_die_bilche@feddit.de 0 points 9 months ago

Collectd on the host sending data to an openwrt docker container. You can view graphs in the openwrt luci ui

[–] ErwinLottemann@feddit.de 0 points 9 months ago

netdata is easy to set up and detects a lot of things on it's own like databases and ntpd and...

[–] MaggiWuerze@feddit.de 0 points 9 months ago

Standard solution would be grafana + Prometheus on one server and a node exporter running on each pi. You then register the node exporters in Prometheus and use that as a data source for grafana. There you build a dashboard showing whatever metrics you want. It can also show some information about the Docker socket, like number of running/stopped containers and such.