Interesting output to graph

[malken00]

Hey everyone,

Just want to start by saying, thank you all for the help you've all given me, over the past month. I am so close to getting this to work, it hurts to think about it


Now, the last problem that I can't seem to solve. I have a script running an snmpget command, which returns the following via log output:

Code: Select all

perl C:/Inetpub/wwwroot/cacti/resource/script_server/2003perf.pl 2c notmypw 192.168.1.1 .1.3.6.1.4.1.15.69.6.94.2, output: 27206

The script checks a perfmon counter that represents an IIS6 individual website's Total bytes/sec. The output is supposed to be in bytes, and appears to be so by checking the perfmon counter that it relates to on my snmp enabled machine.

The problem, is that my graph looks like the attachment. I am not sure why the graph is going up and down as such as it shoudl be using the 'average' column to show the actual graph. Second part, is that if the bytes are only 27206, why is it showing such HUGE numbers for the counters?

Here is the RRDTool debug:

c:/rrdtool2/rrdtool.exe graph - \
--imgformat=PNG \
--start=-86400 \
--end=-300 \
--title="Mencken - BAR Bitsapp + Content" \
--rigid \
--base=1000 \
--height=250 \
--width=750 \
--alt-autoscale-max \
--lower-limit=0 \
--vertical-label="bytes per second" \
--slope-mode \
DEF:a="C\:/Inetpub/wwwroot/cacti/rra/mencken_traffic_in_259.rrd":traffic_in:AVERAGE \
DEF:b="C\:/Inetpub/wwwroot/cacti/rra/mencken_traffic_cont_261.rrd":traffic_cont:AVERAGE \
AREA:a#00CF00:"Bitsapp Bytes / sec" \
GPRINTLAST:"Current\:%8.2lf %s" \
GPRINTAVERAGE:"Average\:%8.2lf %s" \
GPRINTMAX:"Maximum\:%8.2lf %s" \
COMMENT:"Total Out\: 98.81 GB\n" \
LINE1:b#0D006A:"Content Bytes / sec" \
GPRINTLAST:"Current\:%8.2lf %s" \
GPRINTAVERAGE:"Average\:%8.2lf %s" \
GPRINTMAX:"Maximum\:%8.2lf %s" \
COMMENT:"Total Out\: 56.25 GB"
RRDTool Says:

OK

[BSOD2600]

I suggest, if you're only going to collect ONE oid and graph it, you use Cacti's builtin functionality. Create a data template and put that OID in there (generic oid template). It'll be more reliable / faster than calling perl.

As for your problem, did you create that data template as gauge or counter? run rrdtool info on the file it's using and post the output.

Lastly, turn your logging level to medium for a few cycles and watch the number that cacti returns/stores for your query. Is it correct?