Yesterday, Jason A. Smith wrote forth saying... > I have a few questions about ganglia development. I am using ganglia on > RedHat 7.x i386 here. > > 1. I tried the new network metrics that are in the latest cvs version > of the monitoring-core module and was wondering what happens on a dual > NIC computer, is just the first interface counted or does it total all > interfaces when calculating bytes/pkts_in/out? I assume this number is > the rate between measurement intervals, correct?
steve's already answered this question.. and yes he checks for the string "lo" and skips the loopback that way. > 2. I thought I saw a message about adding disk i/o metrics to gmond. > Is this currently in development and will it be in the upcoming 2.5.0 > release? We have a set of scripts that we use to collect some extra > data and publish it through gmetric. Some of the extra parameters we > collect are: # of established tcp connections, various disk i/o stats > from iostat like read/write rates, average wait time and service time > for requests. Parameters like this would be useful to include in the > monitoring core. I haven't seen a TODO list, do you have a set of > parameters that will eventually be included in the core? federico sacerdoti is the author of the disk i/o portion of ganglia. he's just put the code into the CVS today? yesterday? recently. with his code you'll see three new disk metrics: disk_total (in gigs), disk_free and part_max_used. disk_total is the total number of gis of storage on the machine.. disk_free is how much free space you have. part_max_used is the maximum percentage used on any partition on the machine in percentage. so if you see a host with part_max_used at 100.00 then you have a problem. :) > 3. What is the long term development plan for gmetad? Will it always > remain a perl script or will it eventually be rewritten in C? I think I > saw an earlier message about the known problems with gmetad hanging or > dieing because of network problems or hosts not responding. Are there > any ideas on a way to solve this problem? i'm trying it in C right now. i finished the frontend for collecting data from different sources but i haven't build the rrd backend yet. i hope that once we get 2.5.0 out the door next week that i can focus full-time on it. the new gmetad will be completely asyncronous and handle network/host failures much more gracefully then the perl version of gmetad. > 4. Just a warning: Have you ever run gmond on hosts that are using > iptables for local firewalling? I have tried it here and think there is > a bug with the iptables handling of multicast packets. I put in a rule > to accept packets for 239.2.11.71 on port 8649, but several minutes > after starting the iptables firewall, the host stops receiving the > multicast packets from other hosts, it only sees the multicast packets > it sends out. Then after stopping iptables it takes a minute or two > before it starts seeing them from other hosts again. I verified this by > watching the packets with tcpdump on two hosts. I don't have this > problem if I use an equivalent ipchains rule instead of iptables. if you want to allow all multicast add the lines iptables -A INPUT -d 224.0.0.0/4 -j ACCEPT iptables -A OUTPUT -d 224.0.0.0/4 -j ACCEPT to you iptables rules. i've found that it works great for us. > PS. Are suggestions or patches welcome if I have some ideas on > improvements with gmetad or its webfrontend? definitely. federico <[EMAIL PROTECTED]> is the point man for the web frontend and i'm the guy to talk to about gmetad (although everyone if free to work on anything that they like of course). we welcome any help that you are willing to offer. -matt
