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

Bug in metrics counting combined with Routing Policy

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • 2.7 ER1
    • Gateway, System
    • None
    • 8
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • +
    • 3scale 2019-09-30, 3scale 2019-10-14

      For full description, see https://docs.google.com/document/d/1-tO_27qZAEHuTL7rMKe-5PUVQZsyJ61aZ0KdNYBOCM0

      Dev note

      A few test scenarios to try and check how routing and stats behave:

      1. Isolated backends: each backend has its own path without overlapping – Nothing weird should happen here; it's just to set a reliable base for comparing behaviors later.
      2. Empty path: one backend trivially overlaps the others by using an empty path
      3. Path extension: one of the paths extends another backend’s path with a slash plus something to make it unique
      4. Product mapping rules overriding backend mapping rules
      5. Catch-all mapping rule at product level
      6. Catch-all mapping rule at backend level

              Unassigned Unassigned
              cbartlet Catherine Bartlett
              Jakub Smadis Jakub Smadis (Inactive)
              Guilherme Cassolato Guilherme Cassolato
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: