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,
- Add a service with an API backend : https://echo-api.3scale.net:443
- Make an API call
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" ).