Homelab

371 readers

3 users here now

Rules

Be Civil.
Post about your homelab, discussion of your homelab, questions you may have, or general discussion about transition your skill from the homelab to the workplace.
No memes or potato images.
We love detailed homelab builds, especially network diagrams!
Report any posts that you feel should be brought to our attention.
Please no shitposting or blogspam.
No Referral Linking.
Keep piracy discussion off of this community

founded 1 year ago

MODERATORS

communick@selfhosted.forum

rglullis

Monitoring Homelab.. The final battle (alien.top)

submitted 11 months ago by ferreiras2018@alien.top to c/homelab@selfhosted.forum

10 comments fedilink hide all child comments

I have tried Nagios, zabbix, netdata, grafana and all the possible combination of Monitoring system... but still cannot find anything like PRTG.. am i the only one suffering by this? i mean the functionality of PRTG and the installation process are unbetable.

No conf file, no database or apache or rules, is just simple as it should be.

All the rest seems to be hard to maintain, condfigure and make it work.

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

[–] healydorf@alien.top 1 points 11 months ago

Yup. Just my $0.02 -- I wouldn't say there's significant benefit over running a mainstream Linux distro and dropping something like RKE2, k3s, Kind, etc on the hardware. If/when I rebuild this cluster, I'll likely switch back to my existing Ansible roles for RKE2 on Ubuntu. I think the intersection of "people who need a very thin distro for just k8s" and "people running baremetal self-managed k8s" is pretty narrow. All the major cloud vendors already produce a thin distro of their own for "just k8s". Choosing Talos likely adds up fast when you're talking hundreds of clusters and thousands of nodes in colos or on-prem.

I have an ARM based cluster I use for network/CNI labbing which runs k3s on Armbian.