[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [hobbit] Issues with NCV



I already had a newline at the end.  And I did the swapping as well.  What's strange is I threw a random line at the end

Blah: 20

And now I get 4 results instead of 5.

So it seems to always ignore the last name comma value in the set.. very strange.


-----Original Message-----
From: Dan Vande More [mailto:bigdan (at) gmail.com] 
Sent: Thursday, November 19, 2009 6:22 PM
To: hobbit (at) hswn.dk
Subject: Re: [hobbit] Issues with NCV

IIRC correctly, you need a newline at the end of the last one.

If that's not that case, then try swapping the last one and third one
around in an effort to troubleshoot - it may be that the 4th has some
misconfiguration or something.

On Thu, Nov 19, 2009 at 4:18 PM, Tom Moore <Tom.Moore (at) sas.com> wrote:
> I'm tearing my hair out trying to solve this one, hopefully someone can help.
>
> I'm trying to set up a graph using NCV, which has worked great in the past, albeit only graphing one or two values.  I'm trying to send 4 values and it's truncating the last one, i.e. the RRD file only shows 3.
>
> My output is simply this:
>
> -----------
> Bus 1 IO/Sec: 0
> Bus 1 Q-IOs: 46
> Bus 2 IO/Sec: 0
> Bus 2 Q-IOs: 47
> ------------
>
> My hobbitserver.cfg has a line to catch everything:
>
> ------------
> NCV_powermt="*:GAUGE"
> ------------
>
> I run the client side script, and this is what I get from the rrdtool dump
>
> ------------
> <!-- Round Robin Database Dump --><rrd> <version> 0003 </version>
>        <step> 300 </step> <!-- Seconds -->
>        <lastupdate> 1258672448 </lastupdate> <!-- 2009-11-19 18:14:08 EST -->
>
>        <ds>
>                <name> Bus1IOSec </name>
>                <type> GAUGE </type>
>                <minimal_heartbeat> 600 </minimal_heartbeat>
>                <min> NaN </min>
>                <max> NaN </max>
>
>                <!-- PDP Status -->
>                <last_ds> 0 </last_ds>
>                <value> 0.0000000000e+00 </value>
>                <unknown_sec> 238 </unknown_sec>
>        </ds>
>
>        <ds>
>                <name> Bus1QIOs </name>
>                <type> GAUGE </type>
>                <minimal_heartbeat> 600 </minimal_heartbeat>
>                <min> NaN </min>
>                <max> NaN </max>
>
>                <!-- PDP Status -->
>                <last_ds> 46 </last_ds>
>                <value> 1.0800000000e+03 </value>
>                <unknown_sec> 238 </unknown_sec>
>        </ds>
>
>        <ds>
>                <name> Bus2IOSec </name>
>                <type> GAUGE </type>
>                <minimal_heartbeat> 600 </minimal_heartbeat>
>                <min> NaN </min>
>                <max> NaN </max>
>
>                <!-- PDP Status -->
>                <last_ds> 0 </last_ds>
>                <value> 0.0000000000e+00 </value>
>                <unknown_sec> 238 </unknown_sec>
>        </ds>
>
> <!-- Round Robin Archives -->   <rra>
> -----snip------
>
>
> I can rearrange the output from the client script to say:
>
> Bus 2 Q-IOs: 47
> Bus 1 IO/Sec: 0
> Bus 1 Q-IOs: 46
> Bus 2 IO/Sec: 0
>
>
> Then the dump from RRD just has Bus2QIOs, Bus1IOSec, and Bus1QIOs
>
> So it's always dropping the 4th value.
>
> Is there some sort of limitation or bug in NCV that only captures 3 NCVs?
>
>
> Thanks!
>
>
>
> To unsubscribe from the hobbit list, send an e-mail to
> hobbit-unsubscribe (at) hswn.dk
>
>
>

To unsubscribe from the hobbit list, send an e-mail to
hobbit-unsubscribe (at) hswn.dk