RDDTool Spikes when using counters

I use RRDTool with nagios/nagios graph to collect performance data over time. I'm having a problem in that when one of the devices reboots the data gets a spike.

I'm using the counter type in RRDtool and so it subtracts the current value from the last value to figure out how many events have occured since the last time the counter was queried. The problem comes when the router/computer reboots and you have a value of 0 and it compares it to the last time. For instance I have it monitoring users per sec on our web server and when the server reboots for whatever reason it will show a spike of 6M users/sec. This makes the graph go all haywire and it becomes useless.

Is there a way to set rrdtool to ignore values that are less then the previous value? A counter will only go up so this seems like an easy way to fix the issue. I think that MRTG does this by default when dealing counters.

Two things I've read about that I don't want to implement.
Cleaning the values.
I know how to clean the values out via script or via a rrdtool dump and then taking them out by hand and reimporting it, but as you can imagine this isn't cool.
Setting upper limits.
You can have RRDTool disregard values that are out of a specific range, but the problem is that I'd have to set up specific limits on each and to be honest on some of them I don't know what would be reasonable limits. I'm afraid I'd lose useful data if it actually go over my limits.

So anyone know how to set this to ignore entries smaller then the last one?

pubdynAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

NopiusCommented:
> Is there a way to set rrdtool to ignore values that are less then the previous value?

No. This behavior is correct. Many counters are overflowed even once a day.

>  I think that MRTG does this by default when dealing counters.

No, it is not. It has exactly the same problem (or feature). I dealt with cases when network counters really go through 0 and this behavior is correct there.

> Cleaning the values.
> I know how to clean the values out via script or via a rrdtool dump and then
> taking them out by hand and reimporting it, but as you can imagine this isn't cool

It is quite reasonable, why it should be cool :-) ?


> You can have RRDTool disregard values that are out of a specific range, but the problem is that I'd have to set up specific limits on each and to be honest on some of them I don't know what would be reasonable limits. I'm afraid I'd lose useful data if it actually go over my limits.

This also may be used. If you have 64bit counter, you count users/sec connection rate and a real maximum of 100 users/sec, then setup cutoff value for your counter is:
18446744073709547615
that is MAX(64bit)-4*100

or if you use 32 bit counter, this value is 4294966895 = MAX(32bit)-4*100.



0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Network Analysis

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.