Selfhosted

61512 readers

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

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

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

submitted 2 years ago by Aux@lemmy.world to c/selfhosted@lemmy.world

32 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.

you are viewing a single comment's thread
view the rest of the comments

[–] SeeJayEmm@lemmy.procrastinati.org 1 points 2 years ago* (last edited 2 years ago) (1 children)

As someone who used Zabbix and stopped because it's an absolute pig, I'm going to recommend Checkmk.

[–] rtxn@lemmy.world 2 points 2 years ago* (last edited 2 years ago) (2 children)

As someone who used Checkmk Raw (the free edition) and stopped because it's an absolute bastard to set up, I'm going to recommend Zabbix.

I'll specify. Installing Checkmk's agent on the servers was fine, but service discovery is completely unreliable (I could never get through a full discovery before it just hung on something unknown) and the web GUI is very difficult to navigate. Unfortunately most of the documentation only covers the paid version, and community support is pretty bad.

Switching to Zabbix was almost plug-and-play by comparison.

[–] 314xel@lemmy.world 9 points 2 years ago

As someone reading this thread, I'm stuck in an endless loop.

[–] SeeJayEmm@lemmy.procrastinati.org 1 points 2 years ago

As someone who used Checkmk Raw (the free edition) and stopped because it’s an absolute bastard to set up, I’m going to recommend Zabbix.

I feel the same way about Zabbix. I'm not going to pretend that CheckMk is super intuitive but I guess I got over the hump because I don't find it difficult to setup, use, or manage.

The reality is for a homelab setup, probably something like uptime kuma would fit the bill for most people. I wanted something like Zabbix or CheckMk for all the detailed stats that Op is looking for. The longer I use it the more I realize I don't need them 99% of the time and I should probably give something like uptime kuma a try myself.