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

APIcast jaeger trace does not show request uri only the API Provider's backend service

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Major Major
    • 2.9.1 GA
    • 2.8 GA
    • Gateway
    • None
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • +

      In the jaeger trace for an API call through apicast, the http.url shows the API provider's backend service not the request uri. In order to trace the API call effectively, both the request uri as well as the API provider's backend service need to be shown.

      For example,

      The following is shown in different operations for "apicast"

      apicast / :
      http.method: POST
      http.url: "http://echo-api.3scale.net/?<key-redacted>"

      apicast @upstream:
      http.host: echo-api.3scale.net
      http.url: "http://echo-api.3scale.net/?<key-redacted>"

      apicast @out_of_band_authrep_action:
      http.host: echo-api.3scale.net
      http.url: "http://echo-api.3scale.net/?<key-redacted>"

      Both the request uri and the API Provider's backend service (upstream uri) should be shown. These can be shown in different operations with "apicast" span ( eg "/" and "upstream" ).

              Unassigned Unassigned
              rhn-support-cvajjhal Chandrasekhar Vajjhala (Inactive)
              David Rajnoha David Rajnoha (Inactive)
              Eloy Coto Eloy Coto (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: