noob: graph values are off by a factor of 300, can't see why

Post general support questions here that do not specifically fall into the Linux or Windows categories.

Moderators: Developers, Moderators

Post Reply
User avatar
Dinger
Posts: 10
Joined: Fri May 16, 2008 12:43 pm

noob: graph values are off by a factor of 300, can't see why

Post by Dinger »

This is my first custom graph; everything I've used up-till now have been templates.

I am trying to graph an arbitrary OID with Cacti (0.8.7b, rrdtool 1.2.27). I have the SNMP data being captured, and graphed, but the values do not appear to be correct (they kinda of look to be a factor off, but my Unit Exponent Value on the Graph Template is 0).

I am gathering the value of the OID via a simple cron script also (my original method of graphing :wink: ).

Here is the graph: Image

For the same time period, the values were:
Fri May 16 13:10:01 EDT 2008
Counter32: 8575703
-----
Fri May 16 13:15:02 EDT 2008
Counter32: 8575718
-----
Fri May 16 13:20:01 EDT 2008
Counter32: 8578040
-----
Fri May 16 13:25:01 EDT 2008
Counter32: 8578498

Notice how between 13:15 and 13:20 the value changed by 2322. So I figured Cacti would graph a value of 2322, but instead it shows about 8. So at first I thought Cacti was grabbing something wrong, but a rrdtool info of the rrd shows the data gathered is the same as my script.

Can someone whack me with a cluestick please? :) Should I post my .rrd file?
Last edited by Dinger on Sat May 17, 2008 11:34 am, edited 1 time in total.
User avatar
Dinger
Posts: 10
Joined: Fri May 16, 2008 12:43 pm

Post by Dinger »

It looks like all the values are off by a factor of 300; based on my other script, the highest change in value was 37,374, but Cacti reports the highest was 124.49 (37374 / 124.49 = 300)

What could I have wrong to make my graphs off by a factor of 300?
User avatar
gandalf
Developer
Posts: 22383
Joined: Thu Dec 02, 2004 2:46 am
Location: Muenster, Germany
Contact:

Post by gandalf »

COUNTER data sources are reporting rates as "per second". When running standard polling interval of 300 seconds, rrdtool will divide COUNTER values by 300 to get "per second" values.
Reinhard
Post Reply

Who is online

Users browsing this forum: No registered users and 4 guests