Conversation
Notices
-
Dear Interwebs. I want to monitor (read: generate pretty graphs) of my Linode, but collectd is way too I/O and CPU intensive. Suggestions?
-
@jeremyvisser I use cacti, that seems to work even on the crufty VM I run
-
@cafuego If you run `top`, do you see cacti chewing up CPU all day?
-
@cafuego Thanks for the suggestion, BTW. I’ll check it out.
-
@jeremyvisser cacti uses CPU when you hit the page that displays graphs, as they only get generated when viewed.
-
@jeremyvisser collectd actually seemed the most efficient collection tool out there, IMHO. Graph generation could be more efficient
-
@jeremyvisser ...but I don't look at #collectd graphs frequently enough to care.
-
@tamasrepus It certainly seems the most lightweight, configuration– and setting up–wise — definitely not the smallest thing to consider.
-
@jeremyvisser Just checking: you're doing graph generation on a faster machine, right? Perhaps on a local server rather than the Linode
-
@jeremyvisser collectd can act as a "collector", sending statistics to another server. That machine then can write to RRDs/generate graphs
-
@tamasrepus Running it on my local file server. Not yet running it on my Linode. :)
-
@tamasrepus How much bandwidth does it use? If I did that, I’d be sending data home over my ADSL, which is bandwidth metered (evil).
-
@jeremyvisser I'm not sure, it's definitely not noticeable.. will setup an iptables accounting rule and get back to you
-
@tamasrepus How did it go? :)
-
@jeremyvisser Blah... was AFK a couple days, and apparently my iptables accounting rules are wrong. You still need this info?
-
@tamasrepus Nah, not really. It’s running quite nicely served from the machine anyway. Thanks, anyway. :)
-
All Identi.ca content and data are available under the