I don't quite follow Charles. Here's the relevant lines from my hobbitserver.cfg file:
TEST2RRD="cpu=la,disk,inode,qtree,memory,$PINGCOLUMN=tcp,http=tcp,dns=tcp,dig=tcp,time=ntpstat,vmstat,iostat,netstat,temperature,apache,bind,sendmail,mailq,nmailq=mailq,socks,bea,iishealth,citrix,bbgen,bbtest,bbproxy,hobbitd,files,procs=processes,ports,clock,lines,pcpuIdle=ncv"
GRAPHS="la,disk,inode,qtree,files,processes,memory,users,vmstat,iostat, tcp.http ,tcp,ncv,netstat,ifstat,mrtg::1,ports,temperature,ntpstat,apache,bind,sendmail,mailq,socks,bea,iishealth,citrix,bbgen,bbtest,bbproxy,hobbitd,clock,lines,pcpuIdle=ncv"
NCV_pcpuIdle="pcpuIdle:GAUGE"
The message I'm sending from the client is a data message, not a status message. This is what's coming from my client via an ext script running every 5 minutes:
$BB $BBDISP "data $MACHINE.pcpu
cat /tmp/pcpu.txt
"
Sage
On 11/8/06, Charles Goyard <cgoyard at cvf.fr> wrote:
On the server side of things I've modified the hobbitserver.cfg files' TEST2RRD and GRAPHS lines to append "pcpu_idle=ncv". I also have this line in the same file: NCV_pcpu_idle="pcpu_idle:GAUGE"
The problem comes from that your setup should read as :
TEST2RRD="$TEST2RRD,pcpu=ncv" ^-- match the name of the status NCV_pcpu="pcpu_idle:GAUGE" ^-- same thing here
Regards,
--