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

Make hierarchy between the Product and Backends "hits" metric configurable

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • None
    • Backend, System
    • False
    • False
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started

      In certain scenarios, when users define similar mapping rules at Backend and Product level, if a Backend method "hit" is incremented, overall Product "hits" increments also. This double counting causes confusion to some customers. 

      It can be argued that users can decide to create methods mapping rules only at one level (product or backend), but when they do at backend level, the API consumer is unable to see application stats on backed methods hits from the Developer Portal. In this cases, to give stats visibility, they need to create additional product mapping rules also at product level.

      The request is to add an additional flag in the Admin portal (possibly a checkbox) to allow users to decide if they want Backend hits to be also counted as Product hits or not.

       

              Unassigned Unassigned
              amasferr Andreu Masferrer
              Melody Zhong Melody Zhong
              Votes:
              3 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: