[hobbit] Custom graph missing (continued)

[Galen Johnson]

I think your best bet is going to be to somehow split out the rrds to separate files (sensors.brdtmp.rrd, sensors.cpu1tmp, etc).  I haven't had the opportunity to have to attempt this but I'd be very surprised if others haven't. 

Once you get it into separate rrds, and you have a consistent definition in each one, such as temperature, you should be able to try it using the way it was previously defined.

All that said, one thing I am curious about is why the line definition is "LINE2:p at RRDIDX@#@COLOR@:@RRDPARAM@" instead of "LINE at RRDIDX@:p at RRDIDX@#@COLOR@:@RRDPARAM@"?...this question isn't directed at you, Sam.

=G=

-----Original Message-----
From: Sam Przyswa [mailto:samp at arial-concept.com] 
Sent: Monday, October 01, 2007 4:25 PM
To: hobbit at hswn.dk
Subject: Re: [hobbit] Custom graph missing (continued)

Galen Johnson a écrit :
> I've had success with NCV without needing to add the test name to GRAPHS (ncv seems to be sufficient).  What I usually do in the graph config would be to explicitly define my definitions, something like:
>
> [sensors]
>         TITLE Temperature
>         YAXIS Celsius
>         DEF:cpu1tmp=sensors.rrd:CPU1Tmp:AVERAGE
>         DEF:cpu2tmp=sensors.rrd:CPU2Tmp:AVERAGE
>         DEF:brdtmp=sensors.rrd:BrdTmp:AVERAGE
>         LINE1:cpu1tmp#FF0000:CPU-1 Tmp
>         LINE2:cpu2tmp#00FF00:CPU-1 Tmp
>         LINE3:brdtmp#0000FF:CPU-1 Tmp
>         GPRINT:cpu1tmp:LAST: \: %5.1lf (cur)
>         GPRINT:cpu1tmp:MAX: \: %5.1lf (max)
>         GPRINT:cpu1tmp:MIN: \: %5.1lf (min)
>         GPRINT:cpu1tmp:AVERAGE: \: %5.1lf (avg)\n
>         GPRINT:cpu2tmp:LAST: \: %5.1lf (cur)
>         GPRINT:cpu2tmp:MAX: \: %5.1lf (max)
>         GPRINT:cpu2tmp:MIN: \: %5.1lf (min)
>         GPRINT:cpu2tmp:AVERAGE: \: %5.1lf (avg)\n
>         GPRINT:brdtmp:LAST: \: %5.1lf (cur)
>         GPRINT:brdtmp:MAX: \: %5.1lf (max)
>         GPRINT:brdtmp:MIN: \: %5.1lf (min)
>         GPRINT:brdtmp:AVERAGE: \: %5.1lf (avg)\n
>
> It looks like you're pulling from a single rrd (sensors.rrd) instead of multiple rrds (sensors.*.rrd, such as sensors.cpu1tmp.rrd) (which is what the function def looks for).  I'm sure there's a better way but I know adding it manually works.  Of course, if your rrd changes, your graph won't catch it.
>   

Yes it's my problem because I have some mono-proc machines where the 
label is "CPU Tmp" or I have machines with "CPU Fan" and "Brd Fan" how 
can I do ?

Sam.



> -----Original Message-----
> From: Sam Przyswa [mailto:samp at arial-concept.com] 
> Sent: Monday, October 01, 2007 1:36 PM
> To: Hobbit Users List
> Subject: [hobbit] Custom graph missing (continued)
>
> Hi Hobbit users,
>
> I create à custom monitor script to check lm-sensors temperatures from
> Linux boxes named "sensors" the data are sent by the remote client as:
>
> CPU-1 Tmp : 21.88
> Brd Tmp : 19.12
> CPU-2 Tmp : 22.38 > 17 reached! (Warnlevel Yellow)
>
> To respect the name-colon-value formatted report
>
> This is well displayed on the machine's monitor page and the alerts are
> sent by mail as well, but the graph is not create in monitor and trends
> page. I put on server in hobbitserver.cfg
>
> TEST2RRD="cpu=la,...,sensors=ncv
>
> GRAPHS="...,ncv,...,sensors
>
> NCV_sensors="*:GAUGE"
>
> The sensors.rrd dump give:
>
> <!-- Round Robin Database Dump --><rrd> <version> 0003 </version>
>         <step> 300 </step> <!-- Seconds -->
>         <lastupdate> 1191248506 </lastupdate> <!-- 2007-10-01 16:21:46
> CEST -->
>
>         <ds>
>                 <name> CPU1Tmp </name>
>                 <type> GAUGE </type>
>                 <minimal_heartbeat> 600 </minimal_heartbeat>
>                 <min> 0.0000000000e+00 </min>
>                 <max> NaN </max>
>
>                 <!-- PDP Status -->
>                 <last_ds> UNKN </last_ds>
>                 <value> 2.2662800000e+03 </value>
>                 <unknown_sec> 0 </unknown_sec>
>         </ds>
>
>         <ds>
>                 <name> BrdTmp </name>
>                 <type> GAUGE </type>
>                 <minimal_heartbeat> 600 </minimal_heartbeat>
>                 <min> 0.0000000000e+00 </min>
>                 <max> NaN </max>
>
>                 <!-- PDP Status -->
>                 <last_ds> UNKN </last_ds>
>                 <value> 2.0797200000e+03 </value>
>                 <unknown_sec> 0 </unknown_sec>
>         </ds>
>
>         <ds>
>                 <name> CPU2Tmp </name>
>                 <type> GAUGE </type>
>                 <minimal_heartbeat> 600 </minimal_heartbeat>
>                 <min> 0.0000000000e+00 </min>
>                 <max> NaN </max>
>
>                 <!-- PDP Status -->
>                 <last_ds> UNKN </last_ds>
>                 <value> 2.3722800000e+03 </value>
>                 <unknown_sec> 0 </unknown_sec>
>         </ds>
> [...]
>
> And in the hobbitgraph.cfg I have:
>
> [sensors]
>         FNPATTERN sensors.(.+).rrd
>         TITLE Temperature
>         YAXIS Celsius
>         DEF:p at RRDIDX@=@RRDFN@:temperature:AVERAGE
>         LINE2:p at RRDIDX@#@COLOR@:@RRDPARAM@
>         GPRINT:p at RRDIDX@:LAST: \: %5.1lf (cur)
>         GPRINT:p at RRDIDX@:MAX: \: %5.1lf (max)
>         GPRINT:p at RRDIDX@:MIN: \: %5.1lf (min)
>         GPRINT:p at RRDIDX@:AVERAGE: \: %5.1lf (avg)\n
>
> I forget to say this is the 4.2.0 version installed on Ubuntu and some 
> client machine on Debian.
>
> What I have missed ?
>
> Thanks for your help.
>
> Sam.
>   


-- 
Ce message a été vérifié par MailScanner
pour des virus ou des polluriels et rien de
suspect n'a été trouvé.


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