From: Josh L. <jo...@im...> - 2011-05-31 20:28:51
|
I am trying to set up graphs for an APC 9619 (I am using the template from the SF files directory). The dm column appears on the bbdisp host. I am getting the power message on this host on Xymon and I can see the graph reference, but the image is blank/broken. I only have docs/GRAPHING to go by and I followed this by: * --extra-script /usr/share/devmon/extras/devmon-rrd.pl to both rrdstatus and rrddata in tasks.cfg * power=devmon to the end of TEST2RRD in xymonserver.cfg * I'm at a complete loss in what would be accurate in Xymon's graphs.cfg, but I took an example from extras/devmon-graph.cfg and changed a few things. I was hoping to look at the RRD file for examples to help me complete this [power] FNPATTERN power.(.*).rrd TITLE Power YAXIS Volts DEF:in@RRDIDX@=@RRDFN@:ds0:AVERAGE CDEF:inbytes@RRDIDX@=in@RRDIDX@,8,* DEF:out@RRDIDX@=@RRDFN@:ds1:AVERAGE CDEF:outbytes@RRDIDX@=out@RRDIDX@,8,* LINE1:inbytes@RRDIDX@#@COLOR@:@RRDPARAM@ In GPRINT:inbytes@RRDIDX@:LAST: %8.2lf %s (cur) GPRINT:inbytes@RRDIDX@:MAX: %8.2lf %s (max) GPRINT:inbytes@RRDIDX@:MIN: %8.2lf %s (min) GPRINT:inbytes@RRDIDX@:AVERAGE: %8.2lf %s (avg)\n LINE1:outbytes@RRDIDX@#@COLOR@:@RRDPARAM@ Out GPRINT:outbytes@RRDIDX@:LAST: %8.2lf %s (cur) GPRINT:outbytes@RRDIDX@:MAX: %8.2lf %s (max) GPRINT:outbytes@RRDIDX@:MIN: %8.2lf %s (avg) GPRINT:outbytes@RRDIDX@:AVERAGE: %8.2lf %s (avg)\n -l 0 I am looking at the RRD file and the values (min, max, value, etc) are all NaN or 0.0000000000e+00 Can anyone point me in the right direction? Thank you for this much needed addition to Xymon! Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 |
From: Buchan M. <bg...@st...> - 2011-06-01 13:32:11
|
On Tuesday, 31 May 2011 21:58:08 Josh Luthman wrote: > I am trying to set up graphs for an APC 9619 (I am using the template from > the SF files directory). No version of this template has had RRD support for the power test (yet). If you have a temperature sensor, the 'temp' test should though. > The dm column appears on the bbdisp host. I am > getting the power message on this host on Xymon and I can see the graph > reference, but the image is blank/broken. > > I only have docs/GRAPHING to go by and I followed this by: > > * --extra-script /usr/share/devmon/extras/devmon-rrd.pl to both rrdstatus > and rrddata in tasks.cfg This should not be necessary in 4.2.3 or later. > * power=devmon to the end of TEST2RRD in xymonserver.cfg The devmon collector is intended for devmon's TABLE:rrd operator in message files, however the power test doesn't operate on any repeater OIDs. The ncv module may be more appropriate, but it may choke on some of the non-numeric values that follow colons in the message file ... > * I'm at a complete loss in what would be accurate in Xymon's graphs.cfg, > but I took an example from extras/devmon-graph.cfg and changed a few > things. I was hoping to look at the RRD file for examples to help me > complete this > > [power] > FNPATTERN power.(.*).rrd > TITLE Power > YAXIS Volts > DEF:in@RRDIDX@=@RRDFN@:ds0:AVERAGE > CDEF:inbytes@RRDIDX@=in@RRDIDX@,8,* > DEF:out@RRDIDX@=@RRDFN@:ds1:AVERAGE > CDEF:outbytes@RRDIDX@=out@RRDIDX@,8,* > LINE1:inbytes@RRDIDX@#@COLOR@:@RRDPARAM@ In > GPRINT:inbytes@RRDIDX@:LAST: %8.2lf %s (cur) > GPRINT:inbytes@RRDIDX@:MAX: %8.2lf %s (max) > GPRINT:inbytes@RRDIDX@:MIN: %8.2lf %s (min) > GPRINT:inbytes@RRDIDX@:AVERAGE: %8.2lf %s (avg)\n > LINE1:outbytes@RRDIDX@#@COLOR@:@RRDPARAM@ Out > GPRINT:outbytes@RRDIDX@:LAST: %8.2lf %s (cur) > GPRINT:outbytes@RRDIDX@:MAX: %8.2lf %s (max) > GPRINT:outbytes@RRDIDX@:MIN: %8.2lf %s (avg) > GPRINT:outbytes@RRDIDX@:AVERAGE: %8.2lf %s (avg)\n > -l 0 > > > I am looking at the RRD file and the values (min, max, value, etc) are all > NaN or 0.0000000000e+00 > > Can anyone point me in the right direction? Please supply the output of: bb localhost 'hobbitdlog ups.power' or equivalent, where 'ups' is the host name of your APC 9619 in the bb-hosts file. The 'rrdtool info /path/to/file.rrd' would also help shed some light here. Regards, Buchan |
From: Josh L. <jo...@im...> - 2011-06-01 14:31:13
|
>No version of this template has had RRD support for the power test (yet). If >you have a temperature sensor, the 'temp' test should though. I don't have a temp column, should I? I get an answer for the first OID but the humidity is -1. >This should not be necessary in 4.2.3 or later. I'll remove it once everything is working, thanks for the tip. I am running 4.3.2 > bb localhost 'hobbitdlog ups.power' http://pastebin.com/DaySRCTe >rrdtool info /home/xymon/data/rrd/stouderapc/power.rrd http://pastebin.com/2hjKyrXZ Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Wed, Jun 1, 2011 at 9:32 AM, Buchan Milne <bg...@st...>wrote: > On Tuesday, 31 May 2011 21:58:08 Josh Luthman wrote: > > I am trying to set up graphs for an APC 9619 (I am using the template > from > > the SF files directory). > > No version of this template has had RRD support for the power test (yet). > If > you have a temperature sensor, the 'temp' test should though. > > > The dm column appears on the bbdisp host. I am > > getting the power message on this host on Xymon and I can see the graph > > reference, but the image is blank/broken. > > > > I only have docs/GRAPHING to go by and I followed this by: > > > > * --extra-script /usr/share/devmon/extras/devmon-rrd.pl to both > rrdstatus > > and rrddata in tasks.cfg > > This should not be necessary in 4.2.3 or later. > > > * power=devmon to the end of TEST2RRD in xymonserver.cfg > > The devmon collector is intended for devmon's TABLE:rrd operator in message > files, however the power test doesn't operate on any repeater OIDs. The ncv > module may be more appropriate, but it may choke on some of the non-numeric > values that follow colons in the message file ... > > > * I'm at a complete loss in what would be accurate in Xymon's graphs.cfg, > > but I took an example from extras/devmon-graph.cfg and changed a few > > things. I was hoping to look at the RRD file for examples to help me > > complete this > > > > [power] > > FNPATTERN power.(.*).rrd > > TITLE Power > > YAXIS Volts > > DEF:in@RRDIDX@=@RRDFN@:ds0:AVERAGE > > CDEF:inbytes@RRDIDX@=in@RRDIDX@,8,* > > DEF:out@RRDIDX@=@RRDFN@:ds1:AVERAGE > > CDEF:outbytes@RRDIDX@=out@RRDIDX@,8,* > > LINE1:inbytes@RRDIDX@#@COLOR@:@RRDPARAM@ In > > GPRINT:inbytes@RRDIDX@:LAST: %8.2lf %s (cur) > > GPRINT:inbytes@RRDIDX@:MAX: %8.2lf %s (max) > > GPRINT:inbytes@RRDIDX@:MIN: %8.2lf %s (min) > > GPRINT:inbytes@RRDIDX@:AVERAGE: %8.2lf %s (avg)\n > > LINE1:outbytes@RRDIDX@#@COLOR@:@RRDPARAM@ Out > > GPRINT:outbytes@RRDIDX@:LAST: %8.2lf %s (cur) > > GPRINT:outbytes@RRDIDX@:MAX: %8.2lf %s (max) > > GPRINT:outbytes@RRDIDX@:MIN: %8.2lf %s (avg) > > GPRINT:outbytes@RRDIDX@:AVERAGE: %8.2lf %s (avg)\n > > -l 0 > > > > > > I am looking at the RRD file and the values (min, max, value, etc) are > all > > NaN or 0.0000000000e+00 > > > > Can anyone point me in the right direction? > > Please supply the output of: > bb localhost 'hobbitdlog ups.power' > > or equivalent, where 'ups' is the host name of your APC 9619 in the > bb-hosts > file. > > The 'rrdtool info /path/to/file.rrd' would also help shed some light here. > > Regards, > Buchan > |
From: Buchan M. <bg...@st...> - 2011-06-01 14:47:02
|
On Wednesday, 1 June 2011 16:30:44 Josh Luthman wrote: > >No version of this template has had RRD support for the power test (yet). > > If > > >you have a temperature sensor, the 'temp' test should though. > > I don't have a temp column, should I? I get an answer for the first OID > but the humidity is -1. > > >This should not be necessary in 4.2.3 or later. > > I'll remove it once everything is working, thanks for the tip. I am > running 4.3.2 > > > bb localhost 'hobbitdlog ups.power' > > http://pastebin.com/DaySRCTe No RRD "header" for the devmon collector. > >rrdtool info /home/xymon/data/rrd/stouderapc/power.rrd > > http://pastebin.com/2hjKyrXZ Looks like this was collected by NCV, but the values following the "C" are not pure numeric. I would suggest you play with the formatting in the messages file to ensure that lines with a colon are strictly: Name : value Something like this: Index: templates/apc-9619/power/message =================================================================== --- templates/apc-9619/power/message (revision 225) +++ templates/apc-9619/power/message (working copy) @@ -12,12 +12,15 @@ UPS Status: {upsOutStat} Battery Status: {upsBattStat} -Runtime Remaining: {upsMinsRunTime} minutes (red={upsMinsRunTime.thresh:red}m) +Runtime Remaining: {upsMinsRunTime} + - minutes (red={upsMinsRunTime.thresh:red}m) Battery Capacity: {upsBattCap}% UPS Load: {upsLoadOut}% (yellow={upsLoadOut.thresh:yellow}% red={upsLoadOut.thresh:red}%) -Voltage in: {upsVoltageIn}v (yellow={upsVoltageIn.thresh:yellow}v red={upsVoltageIn.thresh:red}v) -Voltage out: {upsVoltageOut}v +Voltage in: {upsVoltageIn} + (yellow={upsVoltageIn.thresh:yellow}v red={upsVoltageIn.thresh:red}v) +Voltage out: {upsVoltageOut} Last failure due to: {upsFailCause} -Time on battery: {upsSecsOnBatt} secs +Time on battery: {upsSecsOnBatt} + - seconds Regards, Buchan |
From: Josh L. <jo...@im...> - 2011-06-01 16:01:00
|
I put that information in the message file and now it is putting that on the Xymon page ( http://172.16.0.114/xymon-cgi/svcstatus.sh?HOST=stouderapc&SERVICE=power ) Looks like this: http://i.imgur.com/dGAzY.png It doesn't look like it's reading it correctly or I told it to do something wrong. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Wed, Jun 1, 2011 at 10:46 AM, Buchan Milne <bg...@st...>wrote: > On Wednesday, 1 June 2011 16:30:44 Josh Luthman wrote: > > >No version of this template has had RRD support for the power test > (yet). > > > > If > > > > >you have a temperature sensor, the 'temp' test should though. > > > > I don't have a temp column, should I? I get an answer for the first OID > > but the humidity is -1. > > > > >This should not be necessary in 4.2.3 or later. > > > > I'll remove it once everything is working, thanks for the tip. I am > > running 4.3.2 > > > > > bb localhost 'hobbitdlog ups.power' > > > > http://pastebin.com/DaySRCTe > > No RRD "header" for the devmon collector. > > > >rrdtool info /home/xymon/data/rrd/stouderapc/power.rrd > > > > http://pastebin.com/2hjKyrXZ > > Looks like this was collected by NCV, but the values following the "C" are > not > pure numeric. I would suggest you play with the formatting in the messages > file to ensure that lines with a colon are strictly: > > Name : value > > Something like this: > > Index: templates/apc-9619/power/message > =================================================================== > --- templates/apc-9619/power/message (revision 225) > +++ templates/apc-9619/power/message (working copy) > @@ -12,12 +12,15 @@ > UPS Status: {upsOutStat} > Battery Status: {upsBattStat} > > -Runtime Remaining: {upsMinsRunTime} minutes > (red={upsMinsRunTime.thresh:red}m) > +Runtime Remaining: {upsMinsRunTime} > + - minutes (red={upsMinsRunTime.thresh:red}m) > Battery Capacity: {upsBattCap}% > UPS Load: {upsLoadOut}% (yellow={upsLoadOut.thresh:yellow}% > red={upsLoadOut.thresh:red}%) > > -Voltage in: {upsVoltageIn}v (yellow={upsVoltageIn.thresh:yellow}v > red={upsVoltageIn.thresh:red}v) > -Voltage out: {upsVoltageOut}v > +Voltage in: {upsVoltageIn} > + (yellow={upsVoltageIn.thresh:yellow}v > red={upsVoltageIn.thresh:red}v) > +Voltage out: {upsVoltageOut} > > Last failure due to: {upsFailCause} > -Time on battery: {upsSecsOnBatt} secs > +Time on battery: {upsSecsOnBatt} > + - seconds > > > Regards, > Buchan > |
From: Buchan M. <bg...@st...> - 2011-06-02 08:12:25
|
I supplied a diff you should have been able to apply to the original messages file. Here is the complete modified messages file: {upsStatus.errors} {upsBattStat.errors} {upsLoadOut.errors} {upsBattRep.errors} {upsVoltageIn.errors} UPS status: Vendor: apc Model: {upsModel} UPS Status: {upsOutStat} Battery Status: {upsBattStat} Runtime Remaining: {upsMinsRunTime} - minutes (red={upsMinsRunTime.thresh:red}m) Battery Capacity: {upsBattCap}% UPS Load: {upsLoadOut}% (yellow={upsLoadOut.thresh:yellow}% red={upsLoadOut.thresh:red}%) Voltage in: {upsVoltageIn} (yellow={upsVoltageIn.thresh:yellow}v red={upsVoltageIn.thresh:red}v) Voltage out: {upsVoltageOut} Last failure due to: {upsFailCause} Time on battery: {upsSecsOnBatt} - seconds Regards, Buchan On Wednesday, 1 June 2011 18:00:33 Josh Luthman wrote: > I put that information in the message file and now it is putting that on > the Xymon page ( > http://172.16.0.114/xymon-cgi/svcstatus.sh?HOST=stouderapc&SERVICE=power ) > > Looks like this: http://i.imgur.com/dGAzY.png > > It doesn't look like it's reading it correctly or I told it to do something > wrong. > > Josh Luthman > Office: 937-552-2340 > Direct: 937-552-2343 > 1100 Wayne St > Suite 1337 > Troy, OH 45373 > > On Wed, Jun 1, 2011 at 10:46 AM, Buchan Milne <bg...@st...>wrote: > > On Wednesday, 1 June 2011 16:30:44 Josh Luthman wrote: > > > >No version of this template has had RRD support for the power test > > > > (yet). > > > > > If > > > > > > >you have a temperature sensor, the 'temp' test should though. > > > > > > I don't have a temp column, should I? I get an answer for the first > > > OID but the humidity is -1. > > > > > > >This should not be necessary in 4.2.3 or later. > > > > > > I'll remove it once everything is working, thanks for the tip. I am > > > running 4.3.2 > > > > > > > bb localhost 'hobbitdlog ups.power' > > > > > > http://pastebin.com/DaySRCTe > > > > No RRD "header" for the devmon collector. > > > > > >rrdtool info /home/xymon/data/rrd/stouderapc/power.rrd > > > > > > http://pastebin.com/2hjKyrXZ > > > > Looks like this was collected by NCV, but the values following the "C" > > are not > > pure numeric. I would suggest you play with the formatting in the > > messages file to ensure that lines with a colon are strictly: > > > > Name : value > > > > Something like this: > > > > Index: templates/apc-9619/power/message > > =================================================================== > > --- templates/apc-9619/power/message (revision 225) > > +++ templates/apc-9619/power/message (working copy) > > @@ -12,12 +12,15 @@ > > > > UPS Status: {upsOutStat} > > Battery Status: {upsBattStat} > > > > -Runtime Remaining: {upsMinsRunTime} minutes > > (red={upsMinsRunTime.thresh:red}m) > > +Runtime Remaining: {upsMinsRunTime} > > + - minutes (red={upsMinsRunTime.thresh:red}m) > > > > Battery Capacity: {upsBattCap}% > > UPS Load: {upsLoadOut}% (yellow={upsLoadOut.thresh:yellow}% > > > > red={upsLoadOut.thresh:red}%) > > > > -Voltage in: {upsVoltageIn}v > > (yellow={upsVoltageIn.thresh:yellow}v red={upsVoltageIn.thresh:red}v) > > -Voltage out: {upsVoltageOut}v > > +Voltage in: {upsVoltageIn} > > + (yellow={upsVoltageIn.thresh:yellow}v > > red={upsVoltageIn.thresh:red}v) > > +Voltage out: {upsVoltageOut} > > > > Last failure due to: {upsFailCause} > > > > -Time on battery: {upsSecsOnBatt} secs > > +Time on battery: {upsSecsOnBatt} > > + - seconds > > > > > > Regards, > > Buchan |
From: Josh L. <jo...@im...> - 2011-06-02 19:23:11
|
Sorry about that, I didn't recognize that format. I made the changes, deleting power.rrd and the file is no longer being generated. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Thu, Jun 2, 2011 at 4:12 AM, Buchan Milne <bg...@st...>wrote: > I supplied a diff you should have been able to apply to the original > messages > file. > > Here is the complete modified messages file: > > > {upsStatus.errors} > {upsBattStat.errors} > {upsLoadOut.errors} > {upsBattRep.errors} > {upsVoltageIn.errors} > > UPS status: > > Vendor: apc > Model: {upsModel} > > UPS Status: {upsOutStat} > Battery Status: {upsBattStat} > > Runtime Remaining: {upsMinsRunTime} > - minutes (red={upsMinsRunTime.thresh:red}m) > Battery Capacity: {upsBattCap}% > UPS Load: {upsLoadOut}% (yellow={upsLoadOut.thresh:yellow}% > red={upsLoadOut.thresh:red}%) > > Voltage in: {upsVoltageIn} > (yellow={upsVoltageIn.thresh:yellow}v > red={upsVoltageIn.thresh:red}v) > Voltage out: {upsVoltageOut} > > Last failure due to: {upsFailCause} > Time on battery: {upsSecsOnBatt} > - seconds > > > Regards, > Buchan > > On Wednesday, 1 June 2011 18:00:33 Josh Luthman wrote: > > I put that information in the message file and now it is putting that on > > the Xymon page ( > > http://172.16.0.114/xymon-cgi/svcstatus.sh?HOST=stouderapc&SERVICE=power) > > > > Looks like this: http://i.imgur.com/dGAzY.png > > > > It doesn't look like it's reading it correctly or I told it to do > something > > wrong. > > > > Josh Luthman > > Office: 937-552-2340 > > Direct: 937-552-2343 > > 1100 Wayne St > > Suite 1337 > > Troy, OH 45373 > > > > On Wed, Jun 1, 2011 at 10:46 AM, Buchan Milne > <bg...@st...>wrote: > > > On Wednesday, 1 June 2011 16:30:44 Josh Luthman wrote: > > > > >No version of this template has had RRD support for the power test > > > > > > (yet). > > > > > > > If > > > > > > > > >you have a temperature sensor, the 'temp' test should though. > > > > > > > > I don't have a temp column, should I? I get an answer for the first > > > > OID but the humidity is -1. > > > > > > > > >This should not be necessary in 4.2.3 or later. > > > > > > > > I'll remove it once everything is working, thanks for the tip. I am > > > > running 4.3.2 > > > > > > > > > bb localhost 'hobbitdlog ups.power' > > > > > > > > http://pastebin.com/DaySRCTe > > > > > > No RRD "header" for the devmon collector. > > > > > > > >rrdtool info /home/xymon/data/rrd/stouderapc/power.rrd > > > > > > > > http://pastebin.com/2hjKyrXZ > > > > > > Looks like this was collected by NCV, but the values following the "C" > > > are not > > > pure numeric. I would suggest you play with the formatting in the > > > messages file to ensure that lines with a colon are strictly: > > > > > > Name : value > > > > > > Something like this: > > > > > > Index: templates/apc-9619/power/message > > > =================================================================== > > > --- templates/apc-9619/power/message (revision 225) > > > +++ templates/apc-9619/power/message (working copy) > > > @@ -12,12 +12,15 @@ > > > > > > UPS Status: {upsOutStat} > > > Battery Status: {upsBattStat} > > > > > > -Runtime Remaining: {upsMinsRunTime} minutes > > > (red={upsMinsRunTime.thresh:red}m) > > > +Runtime Remaining: {upsMinsRunTime} > > > + - minutes (red={upsMinsRunTime.thresh:red}m) > > > > > > Battery Capacity: {upsBattCap}% > > > UPS Load: {upsLoadOut}% (yellow={upsLoadOut.thresh:yellow}% > > > > > > red={upsLoadOut.thresh:red}%) > > > > > > -Voltage in: {upsVoltageIn}v > > > (yellow={upsVoltageIn.thresh:yellow}v red={upsVoltageIn.thresh:red}v) > > > -Voltage out: {upsVoltageOut}v > > > +Voltage in: {upsVoltageIn} > > > + (yellow={upsVoltageIn.thresh:yellow}v > > > red={upsVoltageIn.thresh:red}v) > > > +Voltage out: {upsVoltageOut} > > > > > > Last failure due to: {upsFailCause} > > > > > > -Time on battery: {upsSecsOnBatt} secs > > > +Time on battery: {upsSecsOnBatt} > > > + - seconds > > > > > > > > > Regards, > > > Buchan > |
From: Richard F. <gol...@gm...> - 2011-06-17 01:47:47
|
http://pastebin.com/WY7k37WM is what I've been using for graphing, in case you get an RRD generated via NCV again. I'm guessing you still have TEST2RRD with "power=devmon" instead of "power=ncv" and weren't aware that it doesn't take effect immediately (I think one needs to at least kill|signal the channel=status process). Add to oids: upsVoltageActual: .1.3.6.1.4.1.318.1.1.1.2.2.8.0 : leaf upsReplaceDate : .1.3.6.1.4.1.318.1.1.1.2.1.3.0 : leaf upsCurrentOut : .1.3.6.1.4.1.318.1.1.1.4.2.4.0 : leaf and add at least the first one somewhere in the message. Alternatively, remove it from the graph definition if you're not using it. Your proposed graph definition seems to have some sort of volt byte units. If you're converting from volt bits to volt bytes, you should divide by 8 rather than multiplying. :) It is trying to use a nonexistent "in" value, which doesn't exist as a DS in your RRD, so the units are moot. In my experience, there's no need to patch the message file as Buchan suggested (because, simply stated, the NCV parser starts when it sees a digit or "-" and stops when it sees a non-digit non-period), but I'm not seeing the "C" he mentioned. OTOH, I'm still on 4.2.3. Here's what I use for the NCV parser: NCV_power="BatteryTemperature:GAUGE,RuntimeRemaining:GAUGE,BatteryCapacity:GAUGE,UPSLoad:GAUGE,Voltageactual:GAUGE,Voltagein:GAUGE,Voltageout:GAUGE,Currentout:GAUGE,Timeonbattery:GAUGE,Lastreplacedon:GAUGE" Now that I look at it again, that Lastreplacedon value really oughtn't be there; as implied above, for a date of "05/01/07", it's parsed as (and results in) "5". A drawback of the NCV parser (and a raison d'etre of SPLIT_NCV) is that an RRD can't easily have an DS pruned, last I checked, so I can't remove it without starting over. My TEST2RRD includes "power=ncv" and GRAPHS includes ",power:power|power1|power2," but, again, that's on 4.2.3. |
From: Josh L. <jo...@im...> - 2011-07-18 18:14:11
|
Thanks for getting back to me! This is all way too much effort for me to deploy, but I would like to complete Devmon + Xymon on the VM guest to share with everyone. >I'm guessing you still have TEST2RRD with "power=devmon" instead of "power=ncv" and weren't aware that it doesn't take effect immediately (I think one needs to at least kill|signal the channel=status process). I tend to expect (with Xymon) config files to be read upon start, every few minutes. When testing new territory I tend to restart things to be certain. >and add at least the first one somewhere in the message. Add the first one of what? This is my message: http://pastebin.com/SyDrLc8c >Your proposed graph definition seems to have... I am using your Pastebin in graphs.cfg now. Devmon is giving me more hassle and as it took me a month and a half to thank you, I think that shows I am a bit busy =( Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Thu, Jun 16, 2011 at 9:47 PM, Richard Finegold <gol...@gm...>wrote: > http://pastebin.com/WY7k37WM is what I've been using for graphing, in > case you get an RRD generated via NCV again. I'm guessing you still > have TEST2RRD with "power=devmon" instead of "power=ncv" and weren't > aware that it doesn't take effect immediately (I think one needs to at > least kill|signal the channel=status process). > > Add to oids: > upsVoltageActual: .1.3.6.1.4.1.318.1.1.1.2.2.8.0 : leaf > upsReplaceDate : .1.3.6.1.4.1.318.1.1.1.2.1.3.0 : leaf > upsCurrentOut : .1.3.6.1.4.1.318.1.1.1.4.2.4.0 : leaf > > and add at least the first one somewhere in the message. > Alternatively, remove it from the graph definition if you're not using > it. > > Your proposed graph definition seems to have some sort of volt byte > units. If you're converting from volt bits to volt bytes, you should > divide by 8 rather than multiplying. :) It is trying to use a > nonexistent "in" value, which doesn't exist as a DS in your RRD, so > the units are moot. > > In my experience, there's no need to patch the message file as Buchan > suggested (because, simply stated, the NCV parser starts when it sees > a digit or "-" and stops when it sees a non-digit non-period), but I'm > not seeing the "C" he mentioned. OTOH, I'm still on 4.2.3. > > Here's what I use for the NCV parser: > > NCV_power="BatteryTemperature:GAUGE,RuntimeRemaining:GAUGE,BatteryCapacity:GAUGE,UPSLoad:GAUGE,Voltageactual:GAUGE,Voltagein:GAUGE,Voltageout:GAUGE,Currentout:GAUGE,Timeonbattery:GAUGE,Lastreplacedon:GAUGE" > Now that I look at it again, that Lastreplacedon value really oughtn't > be there; as implied above, for a date of "05/01/07", it's parsed as > (and results in) "5". A drawback of the NCV parser (and a raison > d'etre of SPLIT_NCV) is that an RRD can't easily have an DS pruned, > last I checked, so I can't remove it without starting over. > > My TEST2RRD includes "power=ncv" and GRAPHS includes > ",power:power|power1|power2," but, again, that's on 4.2.3. > > > ------------------------------------------------------------------------------ > EditLive Enterprise is the world's most technically advanced content > authoring tool. Experience the power of Track Changes, Inline Image > Editing and ensure content is compliant with Accessibility Checking. > http://p.sf.net/sfu/ephox-dev2dev > _______________________________________________ > Devmon-support mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devmon-support > |