-
Notifications
You must be signed in to change notification settings - Fork 479
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]: Operation all dosen't return all the trace #2426
Labels
Comments
did you try increasing the Limit number? |
Yes I have also tried to use the batch processor without limitations, but I have the same issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
Using the jaeger ui, if I want to search all the trace, selecting all in the operation form dose not return all the trace.
While if I set the operation field to a specific value like GET I can see traces that I should see also with the "all" option.
We can see filtering by all, I get just 3 trace (and 0 get request ...), while if I explicit GET I can see correctly all the GET.
In addition I have looked the cassandra table traces, where all the trace are stored and in db running a simple distinct on the trace_id I have seen that there are a lot of more distinct trace_id (more than 100).
Steps to reproduce
Expected behavior
I expect that selecting all in the operation enable me to see all the trace that was produced the selected time interval, not just a few.
Relevant log output
No response
Screenshot
No response
Additional context
No response
Jaeger backend version
No response
SDK
No response
Pipeline
No response
Stogage backend
cassandra
Operating system
Windows(WSL2)
Deployment model
docker compose
Deployment configs
The text was updated successfully, but these errors were encountered: