Same thing, I should imagine. I've never seen this bug present anywhere else.
Is the device being polled quite far away? Or attached on the end of some string?
What is the measurement directly before the spike?
adam.
On Wed, 16 Nov 2011 08:20:19 -0500, Berant Lemmenes berant@lemmenes.com wrote:
The same bill entry that I first reported an issue with has had another 8Gib/s spike as you can see attached below.
I'm up for assisting in anyway to help root this out.
Thanks.
On Fri, Nov 11, 2011 at 4:50 PM, Berant Lemmenes berant@lemmenes.comwrote:
Here is the current counter for that interface:
IF-MIB::ifHCInOctets.1908 = Counter64: 644216574
Yeah, and I imagine people don't want oddities happening in billing during a re-write.
Is there anything else I can provide to help narrow things down?
Thanks, Berant
On Fri, Nov 11, 2011 at 3:48 PM, Adam Armstrong adama@memetic.org wrote:
Hmm. That is very bizarre.
What is the current counter for that interface? My only guess is that
it
for whatever reason managed to not get the "previous" value from the database, and kept inserting current-0 = delta, giving you a value of "current total as if it had all ahppened in the last 5 minutes" for
the
period of time the bug manifested.
The billing code is a little weird, it's very old. I REALLY, REALLY
want
to clean it up, but because people are now using it, it's a little difficult :)
adam.
On Fri, 11 Nov 2011 14:51:58 -0500, Berant Lemmenes berant@lemmenes.com wrote:
Hello,
I've just recently setup Observium and noticed a strange spike in
reported
usage for one billing item, that wasn't reported in the actual
interfaces
stats.
I've attached three screen shots, one of the accurate billing page
for
the
billing entry in question, the 2nd for the interface page under the
device,
and the 3rd for the same interface as seen from a cricket install.
As you can see the physical interface graphs in Observium or cricket
don't
show this extended period of ~ 8Gb/s that show up in the mysql based graphs.
Looking at bill_data for the bill_id in question there were 45
entries
where in_delta was exactly 309525032051591 while out_delta continues to change. Here is an example row:
31, 2011-11-10 17:35:06, 299, 309525032052787, 309525032051591, 1196
This has only manifested in this one billing.
Let me know if there is anything else I can look at or provide that
would
assist.
Thank you in advance.
Thanks, Berant
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium