-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature]: Support external URL prefix #5157
Comments
We have an example Implementation-wise, Jaeger-UI uses jaeger/cmd/query/app/static_handler.go Line 90 in e08f576
It also injects that path into the main index.html as base, and the UI uses it when constructing URLs (both assets and API paths). jaeger/cmd/query/app/static_handler.go Lines 142 to 147 in e08f576
Basically we combine the internal view of the URLs as seen by the query server and the external URLs used by the browser, and by using a single |
I'll work on it. |
@yurishkuro Is this issue resolved or can i take it up? |
It's not resolved afaik, you can see discussion in the linked PR #5219 |
Requirement
There are 2 prefixes, local (current implementation) and external (to be used from the UI). Jaeger supports the local prefix and does not support external prefix currently.
Please check the below discussion for more details.
https://github.com/orgs/jaegertracing/discussions/5042#discussioncomment-8236479
Problem
The traffic flow is gateway>virtual service>gateway>jaeger query.
We are setting the query_base_path as "/jaeger/viewer" and then doing the rewrite using the virtual service configuration mentioned below.
We are getting issue in the Jaeger UI.The index.html is getting loaded but the static files like index.js, index.css are showing loading error(404 not found) in the console tab of the browser.
Proposal
No response
Open questions
No response
The text was updated successfully, but these errors were encountered: