[hobbit] ncv problem
Charles Jones
jonescr at cisco.com
Wed Oct 4 20:38:49 CEST 2006
Sorry for typo, fixed below
> Try removing the extra quotes you added to TEST2RRD. In other words,
> instead of using:
> drops="ncv",
>
> Juse use:
> drops=ncv,
>
> Another thing that I'm not sure about is how you defined
> NCV_drops="*:DERIVE"
> My thoughts on this are:
> 1. Not sure if you can use * as the DS name, I think this should be
> NVC_drops="fdrops:DERIVE" NCV_drops="fdrops:DERIVE"
> 2. DERIVE is the default DS type, so you may not even have to specify
> those at all.
>
> I'm new to NCV graphs myself, so I am just speculating here and trying
> to help.
> -Charles
>
> Jeff Newman wrote:
>> Hi,
>>
>> Running on the new hobbit server, I am seeing these in
>> /var/log/hobbit/status.log:
>>
>> 2006-10-03 18:05:32 Setup error: Service wraps has a graph "ncv", but
>> no graph-definition
>> 2006-10-03 18:05:32 Setup error: Service HiFlowNet has a graph "ncv",
>> but no graph-definition
>> 2006-10-03 18:05:32 Setup error: Service drops has a graph "ncv", but
>> no graph-definition
>>
>> I did not see these until I upgraded to the new server version.
>>
>> Some other info:
>>
>> from hobbitserver.cfg
>>
>> 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,sar,socks,bea,iishealth,citrix,bbgen,bbtest,hobbitd,HiFlowNet="ncv",sock="ncv",qmeter,rtt="ncv",drops="ncv",wraps="ncv",bbproxy,HiFlowNetInt,files,procs=processes,ports,clock,lines"
>>
>>
>> # This defines which RRD files to include on the "trends" column
>> webpage,
>> # and the order in which they appear.
>> GRAPHS="la,disk,inode,qtree,memory,users,vmstat,iostat,tcp.http,tcp,netstat,mrtg::1,temperature,ntpstat,apache,bind,sendmail,mailq,socks,bea,iishealth,citrix,bbgen,bbtest,bbproxy,hobbitd,ncv,HiFlowNet,sock,rtt,wraps,sar::1,qmeter::1,HiFlowNetInt,drops,files,processes,ports,ifstat,clock,lines"
>>
>>
>> NCV_sock="established:GAUGE,synsent:GAUGE,synrecv:GAUGE,finwait1:GAUGE,finwait2:GAUGE,timewait:GAUGE,closed:GAUGE,closewait:GAUGE,lastack:GAUGE,listen:GAUGE,closing:GAUGE,unknown:GAUGE"
>>
>>
>> NCV_rtt="rtt:GAUGE"
>>
>> ** I tried adding the below, and restarting hobbit, and it did not fix
>> the problem **
>> NCV_wraps="*:DERIVE"
>> NCV_drops="*:DERIVE"
>> NCV_HiFlowNet="*:DERIVE"
>>
>> From hobbitgraph.cfg (just to show they are in there)
>>
>> [wraps]
>> TITLE Wraps per second
>> YAXIS Number of wraps
>> DEF:wraps=wraps.rrd:wraps:AVERAGE
>> CDEF:fwraps=wraps,100,*
>> AREA:fwraps#00CC00:Number of wraps
>> -u 1
>> -l 0
>> GPRINT:fwraps:LAST: \: %5.1lf (cur)
>> GPRINT:fwraps:MAX: \: %5.1lf (max)
>> GPRINT:fwraps:MIN: \: %5.1lf (min)
>> GPRINT:fwraps:AVERAGE: \: %5.1lf (avg)\n
>> [drops]
>> TITLE Drops per second
>> YAXIS Number of drops
>> DEF:drops=drops.rrd:drops:AVERAGE
>> CDEF:fdrops=drops,100,*
>> AREA:fdrops#00CC00:Number of drops
>> -u 1
>> -l 0
>> GPRINT:fdrops:LAST: \: %5.1lf (cur)
>> GPRINT:fdrops:MAX: \: %5.1lf (max)
>> GPRINT:fdrops:MIN: \: %5.1lf (min)
>> GPRINT:fdrops:AVERAGE: \: %5.1lf (avg)\n
>> [HiFlowNet]
>> TITLE Network I/O HIGH FLOW
>> YAXIS Bytes/second
>> DEF:tcpInInorderBytes=HiFlowNet.rrd:tcpInInorderBytes:AVERAGE
>> DEF:tcpOutDataBytes=HiFlowNet.rrd:tcpOutDataBytes:AVERAGE
>> LINE1:tcpInInorderBytes#00FFFF:In Total
>> LINE1:tcpOutDataBytes#0000FF:Out Total
>> COMMENT:\n
>> GPRINT:tcpInInorderBytes:LAST:In \: %5.1lf%s (cur)
>> GPRINT:tcpInInorderBytes:MAX: \: %5.1lf%s (max)
>> GPRINT:tcpInInorderBytes:MIN: \: %5.1lf%s (min)
>> GPRINT:tcpInInorderBytes:AVERAGE: \: %5.1lf%s (avg)\n
>> GPRINT:tcpOutDataBytes:LAST:Out \: %5.1lf%s (cur)
>> GPRINT:tcpOutDataBytes:MAX: \: %5.1lf%s (max)
>> GPRINT:tcpOutDataBytes:MIN: \: %5.1lf%s (min)
>> GPRINT:tcpOutDataBytes:AVERAGE: \: %5.1lf%s (avg)\n
>>
>> Some of the other NCV stuff works fine, not sure why those aren't.
>> Any ideas?
>>
>> -Jeff
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20061004/fea13e23/attachment.html>
More information about the Xymon
mailing list