Skip to content
Register

What do you use for internal server monitoring?

General Discussion by blogfranck 4 replies 187 views
blogfranck

Member OP

#1

After three years with hosting at OVHcloud, finally moving monitoring stack from ssh + free -h to something proper. Evaluated:

  • Netdata: beautiful, eats 150MB RAM on my 1GB KnownHost VPS. The graphs are nice but the agent is heavy
  • Zabbix: enterprise horse, needs database, too much for homelab
  • UptimeKuma: simple, Docker one-liner, but only uptime not metrics depth

Currently settled on Netdata with streaming to central node. The config for the parent:

[stream]
enabled = yes
destination = tcp:10.0.0.5:19999
api key = 11111111-2222-3333-4444-555555555555

Anyone running lighter? The budget is tight, voilà.

MI

Member

#2

Netdata bloated. 150MB unacceptable. Server good. Price bad. Network okay.

Ssh. Free -h. df -h. Uptime. Done.

Perkele.

admin

Administrator

Administrator

#3

What kernel version on that KnownHost box

sudo make me a sandwich
haroldgsm

Member

Grumpy Old Sysadmin

#4

150MB for an agent? That's with streaming disabled, surely.

IPv4, IRC, and irssi — fight me
PetraSuper

Member

network boot believer

#5

Same issue with netdata on my 1GB box, had to swap

boot anything, anywhere, anytime

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft