![](https://secure.gravatar.com/avatar/0fa97865a0e1ab36152b6b2299eedb49.jpg?s=120&d=mm&r=g)
On Thu, 13 Oct 2011 12:15:30 +0400, Nikolay Shopik shopik@inblock.ru wrote:
On 05/09/11 19:52, Adam Armstrong wrote:
If we get a set of rules to detect when something is broken, we can return "NA" to rrdtool, which signals it that something is wrong and to not use that value for calculation.
I think this is best approach, and most safe. If something goes wrong always write "NA" to rrdtool. This prevent these peaks in 99% cases.
It's virtually impossible to build such a set of rules though, which is why the problem is so great.
It's difficult to use ifSpeed to 'guess' the speed of the interface, as it's not always correctly reported, particularly on virtual interfaces.
People with 16x10G trunks would be very annoyed if we started returning NAN for measurements above 10G!
adam.