Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-6651

Avoid creating stats keys with value "0"

XMLWordPrintable

    • False
    • False
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • -
    • Undefined

      The problem was that backend was reporting usages of 0 when they were included in requests to the authrep and report endpoints. Because of that, report jobs ended up creating stats keys with a value of 0. A stats key set to 0 is equivalent to a non-existing one when rate-limiting, so the feature was working correctly but wasting space in the DB.

              Unassigned Unassigned
              dortiz-1 David Ortiz (Inactive)
              Petr Hála Petr Hála (Inactive)
              David Ortiz David Ortiz (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: