Details

    • Help
    • Resolution: Fixed
    • Critical
    • None
    • Enterprise Edition
    • Billing
    • Ubuntu 22.04. vSphere

    Description

      Occasionally we have to make changes to the allowed threshold on a bill. What we have discovered is that those changes are not being respected when the billing period ends, so when we look at the previous period it shows the old allowed threshold.

      The bill in the attached screenshot was changed from 50mbps to 100mbps on January 26, 2024, but the previous period is reflecting the old 50mbps allowed threshold.

      We have an old Observium server that is being replaced by the server experiencing this issue, that does not exhibit this issue. Is there something I can adjust to make this work correctly?

       

      Attachments

        Activity

          [OBS-4752] Billing Changes

          And by bill record i mean the entry in `bill_history` with the bill_id matching the bill, between and the correct period.

          if there are missing periods, the billing system will automatically regenerate them

          adama Adam Armstrong added a comment - And by bill record i mean the entry in `bill_history` with the bill_id matching the bill, between and the correct period. if there are missing periods, the billing system will automatically regenerate them

          Oh, and if you're adventurous you can delete this bill record from the database and it'll auto-regenerate now with the correct allowed value.

          (and the legends on those buttons need to be dropped by 1px, but i think doing it raises the legend on some buttons elsewhere, because i'm sure i've been continually fixing this for years!)

          adama Adam Armstrong added a comment - Oh, and if you're adventurous you can delete this bill record from the database and it'll auto-regenerate now with the correct allowed value. (and the legends on those buttons need to be dropped by 1px, but i think doing it raises the legend on some buttons elsewhere, because i'm sure i've been continually fixing this for years!)

          Ahh I see.

          We weren't updating datefrom/dateto/type/allowed fields from the bill on the interim record when updating it.

          It should update these fields from r13298

          Thanks,

          adam.

          adama Adam Armstrong added a comment - Ahh I see. We weren't updating datefrom/dateto/type/allowed fields from the bill on the interim record when updating it. It should update these fields from r13298 Thanks, adam.
          jhunt@ussignal.com Joey Hunt added a comment -

          Hi Adam,

          Yes, I changed it on January 26, 2024 from 50mbps to 100mbps. The screenshot is showing that even though I changed the allowed during the previous billing period and it adjusted the graphing an everything at that time when it was the current billing period. However, now when I go back to the previous period billing it's using the former allowed of 50mbps as the allowed.

          Current Period

          Previous Period

          jhunt@ussignal.com Joey Hunt added a comment - Hi Adam, Yes, I changed it on January 26, 2024 from 50mbps to 100mbps. The screenshot is showing that even though I changed the allowed during the previous billing period and it adjusted the graphing an everything at that time when it was the current billing period. However, now when I go back to the previous period billing it's using the former allowed of 50mbps as the allowed. Current Period Previous Period

          Hi,

          it's not really clear what the problem is, are you sure the threshold was actually changed? It's not changed in the screenshot.

          Thanks,

          adam.

          adama Adam Armstrong added a comment - Hi, it's not really clear what the problem is, are you sure the threshold was actually changed? It's not changed in the screenshot. Thanks, adam.

          People

            adama Adam Armstrong
            jhunt@ussignal.com Joey Hunt
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: