jaeger-ui search filter by duration is misleading #4111
Replies: 4 comments 4 replies
-
It is likely that a span of If any span of a trace satisfies the filter, the trace should appear in the search result. The code of memory storage and Elasticsearch storage can confirm this. memory storage: jaeger/plugin/storage/memory/memory.go Lines 246 to 253 in 3d67ac8 Elasticsearch storage: jaeger/plugin/storage/es/spanstore/reader.go Lines 509 to 564 in 3d67ac8 |
Beta Was this translation helpful? Give feedback.
-
makes me more confused. |
Beta Was this translation helpful? Give feedback.
-
As you see, there are 87 spans in the |
Beta Was this translation helpful? Give feedback.
-
Correct - duration filter applies to individual spans, not to the duration of the whole trace or the root span. |
Beta Was this translation helpful? Give feedback.
-
What happened?
I set
max duration
andmin duration
in jaeger-ui, but it seems not work well.Steps to reproduce
max duration
andmin duration
in jaeger-uiExpected behavior
works well
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
No response
Operating system
No response
Deployment model
No response
Deployment configs
No response
Beta Was this translation helpful? Give feedback.
All reactions