I'm the developer of a performance monitoring tool called collectl - see
http://collectl.sourceforge.net/ which is a fairly light-weight data
collector, capable of collecting most relevant performance metrics. In
addition to the basics that most tools collect like cpu, memory, disk
and
This uses 3.1 Here's an example of the output I generate when debugging is
turned on:
I have a routine I pass 3 parameters to: name of the variable, its units and
the value. I generate 2 packets, the first with a header and the second with
the data, which looks like this:
13:41:45.014
btw I have a suggestion for gmond's debugging output. When I was testing my
collectl interface and used my option to only send changes to gmond I naturally
turned on debugging to see what gmond was getting. I found the output very
difficult to follow since every received packet generated 3
The only thing that I would suggest is that you use the APIs to create and send
the packets. The problem with hand crafting the packets is that if the gmond
XDR packet definition ever changes, your interface will be broken. I don't
foresee the XDR packet definition change very frequently,
