Details
-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
None
-
None
-
Observium 0.13.3.3829
Linux observium 2.6.32-44-generic #98-Ubuntu SMP Mon Sep 24 17:27:10 UTC 2012 x86_64 GNU/Linux
squeeze/sid
Description
It seem to bee observium are not able to detect counter-wraps. (I think so)
We have much Ports with impossible traffic-values on our billing (see attached screenshot with the 30GBit Peak on a 1GBit Interface).
This bug is a blocker for billing!
Maybe observium need a OutOfRange-Feature like in RTG.
Our RTG Billing ist absolutly correct.
Here are a explanation for the OutOfRange Feature in RTG:
The OutOfRange (OOR) setting in rtg.conf is just a sanity check to keep
bogus data from entering the database. For example, rtg is polling a
64bit OID on a router; the last value returned was 100. The router is
rebooted before the next poll. On the next poll, the router returns 50
for this OID. RTG must assume this was a counter wrap, so the delta value
is: 2^64 - 100 + 50, corresponding to approximately 4^17 bps which is
clearly impossible. This is where the OOR comes into play. It is simply
a sanity check that is set to a reasonable value. 93750000000 * 8 / 300 ~=
2.5Gbps, so most people will not want or need to adjust the OOR setting.
Attachments
Activity
For the billing you can just remove the offending entry from the database. Look in billing_data and sort by one of the delta fields 
I've seen this on a Port recently.
observium is reporting a Spike of over 300Mbit/s however the Port is actually an L2TP interface on a Mikrotik Routerboard where the Physical WAN it's connected to is only capable of about 5Mbit/s.
It's therefore trying to tell me that for the month in question the connection hit 2.92TB of transfer, I believe the Mikrotik unit was rebooted just prior to the Spike so I suspect it's a counter wrap that went undetected, I was able to use remove-spikes for the RRD graphs for this port but that doesn't affect the billing displays.
I am also seeing the same issue on our instance.
Observium 0.13.5.4073
Apache 2.2.22 (Ubuntu)
PHP 5.3.10-1ubuntu3.6
MySQL 5.5.31-0ubuntu0.12.04.1
RRDtool 1.4.7
The switch port in question is up at 100mbit, so its impossible to get 5gbit over it.
It is also showing in the port in RRD tool.
I will update this if I can work our a reliable way to replicate the issue, as it is happening to atleast 3 - 4 ports on a daily basis for me.
I think an interface which will allow you to remove spikes greater than $n from the database would be helpful.
There where already adjustments made on the billing poller so it would take care of counter wraps, since the adjustments no one else reported the same problem and i am unable to reproduce it. You can however delete the delta counter from the database and that will also remove the spikes on the graphs and billing pages should return correct values.
I'm busy on new tool section for the billing that will make it able to remove spikes from the billing gui, expect the code to be committed soon.