-
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
[Bug]: The results filtered through the tag in the findtrace
page did not match expectations
#5290
Comments
did you try the advice in the tooltip? (the tooltip has a typo, I put a fix jaegertracing/jaeger-ui#2224) |
Thank you for your reply.
|
@JaredTan95 What is the backend you are using? |
|
quotes around the value: |
Thank you for your reply, but according to your reply, it is still not effective |
What happened?
No data is found when filtering traces through the following tag:
http.url=http://sss.xxx.com/v1/user/spaces/1310e65f-16c6-4502-a9ef-15e0ff38e8b2/zone_roles?service_name=ss.sss.xxx.com
,Is it because the value contains the special symbol
=
at the end? Because passing the following query is normal:http.url=http://sss.xxx.com/v2/healthchaeck
Steps to reproduce
Filter traces data through the following tags:
http.url=http://sss.xxx.com/v1/user/spaces/1310e65f-16c6-4502-a9ef-15e0ff38e8b2/zone_roles?service_name=ss.sss.xxx.com
,Expected behavior
Filter out the data correctly
Relevant log output
No response
Screenshot
Additional context
No response
Jaeger backend version
1.49.0
SDK
No response
Pipeline
No response
Stogage backend
No response
Operating system
No response
Deployment model
No response
Deployment configs
No response
The text was updated successfully, but these errors were encountered: