Details

    • Bug
    • Resolution: Fixed
    • Major
    • None
    • Professional Edition
    • Billing

    Description

      When we open billing historical usage page, we see a lot on inconsistencies in periods.
      Screenshot attached.

      Attachments

        1. observium_billing.jpg
          156 kB
          Eduardo Schoedler
        2. screenshot-1.png
          10 kB
          Eduardo Schoedler

        Activity

          [OBS-4518] Billing history with wrong periods

          It's resolved.
          Thanks.

          eschoedler Eduardo Schoedler added a comment - It's resolved. Thanks.

          You just need to regenerate the historical billing records to fix this.

          ./billing-calculate.php -r

          adam.

          adama Adam Armstrong added a comment - You just need to regenerate the historical billing records to fix this. ./billing-calculate.php -r adam.

          Hi,
          Any updates on this?
          Still showing wrong ranges in Historical Usage of billing.
          Thanks

          eschoedler Eduardo Schoedler added a comment - Hi, Any updates on this? Still showing wrong ranges in Historical Usage of billing. Thanks

          Hi Mike,

          We are using Billing Type: CDR / 95th.

          Here is at revision 12845 and we still see this behavior.

          Thanks!

          eschoedler Eduardo Schoedler added a comment - Hi Mike, We are using Billing Type: CDR / 95th. Here is at revision 12845 and we still see this behavior. Thanks!

          Up up
          which type of billing you use here?

          landy Mike Stupalov added a comment - Up up which type of billing you use here?

          General questions and device support can be discussed in our Discord channel, click here to join.


          Please make and attach additional information about the device:

          • full snmp dump from device:

            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk
            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

            If device not support SNMP version 2c, replace -v2c with -v1.

          • If you have problems with discovery or poller processes, please do and attach these debugs:

            ./discovery.php -d -h <device>
            ./poller.php -d -h <device>

          • additionally attach device and/or vendor specific MIB files

          This comment is added automatically.

          bot Observium Bot added a comment - General questions and device support can be discussed in our Discord channel, click here to join . Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk If device not support SNMP version 2c, replace -v2c with -v1. If you have problems with discovery or poller processes, please do and attach these debugs: ./discovery.php -d -h <device> ./poller.php -d -h <device> additionally attach device and/or vendor specific MIB files This comment is added automatically.

          People

            adama Adam Armstrong
            eschoedler Eduardo Schoedler
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: