Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-264

Impossible high traffic value on traffic-billing

Details

    • Bug
    • Resolution: Fixed
    • Critical
    • None
    • None
    • Billing
    • 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

          People

            codekiller Dennis de Houx
            clusterkiller Michael
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: