-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Can not filter by “Duration (μs)> =” in the UI #1349
Comments
the duration query depends a lot on how your apps are instrumented and
which storage is in use. For example, we no longer support duration query
on the "cassandra" storage type.
|
@longinhit it's supported in the cassandra3 storage, if you're able to upgrade. |
what instrumentation are you using? are the traces you are sending
reporting span.duration? You can check by using the api as
/api/v1/trace/trace-id-in-hex?raw
|
fyi here's a status report on libraries that properly address
timestamp and duration
openzipkin/openzipkin.github.io#49
|
We are using brave v3.15.1. We were previously using v3.9.1 until a few weeks ago and that is around when we started seeing the problem (upgraded brave and zipkin-server jar). We do use a custom jmeter setup to run automated tests and we generate a traceId before sending the initial request so that we can log traceIds alongside request logs. Using the raw endpoint I am seeing sr and ss on the top-level span but it looks like the duration field is missing from that span. Again, this was working previously - is this something that has changed during the deprecation of the |
I verified that when I hit an endpoint using curl and specifying a traceId in the headers the duration does not show up. Without the headers it does. And we found this comment that says a timestamp/duration won't be kept if a traceId is sent - perhaps the cause? https://github.com/openzipkin/brave/blob/181a2f438e5142510cb72eefc723839bc525fe4d/brave-core/src/main/java/com/github/kristofa/brave/ServerRequestInterceptor.java#L50 Does a backfilling as mentioned in the comment ever happen? |
I'll look into this now. It it is a root span, we should be setting
duration for sure. Stand by and thanks for gathering the details!
|
This issue was moved to openzipkin/brave#277 |
No description provided.
The text was updated successfully, but these errors were encountered: