[rrd-users] Using Maximum values to avoid spikes?

[Robert C. Seiwert]

The problem I think is that COUNTER only detects a reset at the 32bit or 64bit border.

I think that DERIVE would give you a negative spike. You might try DCOUNTER. This is floating point which I know is not ideal for the application. The only substantial difference to COUNTER is that DCOUNTER can either be upward counting or downward counting, but not both at the same time. The current direction is detected automatically on the second non-undefined counter update and any further change in the direction is considered a reset. The new direction is determined and locked in by the second update after reset and its difference to the value at reset.

BTW,  Nice garden!

-----Original Message-----
From: rrd-users [mailto:rrd-users-bounces+rob=vcaglobal.com at lists.oetiker.ch] On Behalf Of Florio, Christopher N
Sent: Thursday, August 20, 2015 2:20 PM
To: rrd-users at lists.oetiker.ch
Subject: [GRAYMAIL] [rrd-users] Using Maximum values to avoid spikes?

Hey all,

I've got a home brew rrd file that I've made to keep track of ISC bind statistics.

I've set the max to 4,000,000,000 .... I acrtually see one of my hosts do 1.5G every night for a couple hours.

/usr/bin/rrdtool create \
/usr/share/cacti/rra/crush_net_unc_edu_query_116761.rrd \ --step 300  \
DS:query:COUNTER:600:0:4000000000 \
DS:notify:COUNTER:600:0:4000000000 \
RRA:AVERAGE:0.5:1:500 \
RRA:AVERAGE:0.5:1:600 \
RRA:AVERAGE:0.5:6:700 \
RRA:AVERAGE:0.5:24:775 \
RRA:AVERAGE:0.5:288:797 \
RRA:MAX:0.5:1:500 \
RRA:MAX:0.5:1:600 \
RRA:MAX:0.5:6:700 \
RRA:MAX:0.5:24:775 \
RRA:MAX:0.5:288:797 \

So, what happens is, if the bind process gets restarted, the data goes back to zero and I get a 4G spike on my graph.

Any ideas on fixing that?  Should I use derive instead of counter to fix it up?