Cannot find operations in jaeger-ui, if there is '/' char in serviceName

[niuhf0452]

[yurishkuro]

good catch.

cc @tiffon

[yurishkuro]

Re-booked as a UI issue jaegertracing/jaeger-ui#138

[tiffon]

@yurishkuro looks like merging jaegertracing/jaeger-ui#140 surfaced an issue in jaeger-query.

I ran the hotrod demo with the service names to have jaeger/ prepended. The request to get operations for jaeger/customer is GET for the following URL:

http://localhost:16686/api/services/jaeger%2Fcustomer/operations

The query service responds with the index.html.

Seems like this ticket should be reopened.

[yurishkuro]

arrrg... Should we just switch to the ?service= API?

[yurishkuro]

@tiffon we may have to switch the UI to /api/operations?service=, because I just ran a test (#736) and it doesn't look like Gorilla router we're using is able to deal with / in the middle of the parameter, even if it's url-encoded.

[tiffon]

@yurishkuro I think Gorilla might have a facility for handling this (if I followed correctly):

API: http://www.gorillatoolkit.org/pkg/mux#Router.UseEncodedPath

Related ticket: gorilla/mux#77

Changes that are referenced:

• gorilla/mux@0a192a1
• gorilla/mux@c9183aa

[yurishkuro]

true, I was able to fix the test, but I still think that we should do what we planned long time ago - only support /api/operations?service= API and remove all this duplicated / special-cased code from query service.