The duration of an async one way span is not captured on the Zipkin UI. The span is shared across processes, with only ‘cs’ and ‘sr’ annotations captured at the client and server side respectively. There is an explicit Start and flush in both client and server. No spam.finish invoked anywhere. The trace json from the zipkin server shows 2 spans with the same Id, each having the correct time stamp and no duration. I effectively want to see the duration of this entire span from Cs to Sr . - I see this information on the right tab of the span as ‘Relative Time’ under the ‘Server Start’ annotation. But the actual span does not show the duration bar.
Using 2.21 version of zipkin with inmemory storage and java brave client library.
Am I missing anything, or is this the expected behaviour?
The duration of an async one way span is not captured on the Zipkin UI. The span is shared across processes, with only ‘cs’ and ‘sr’ annotations captured at the client and server side respectively. There is an explicit Start and flush in both client and server. No spam.finish invoked anywhere. The trace json from the zipkin server shows 2 spans with the same Id, each having the correct time stamp and no duration. I effectively want to see the duration of this entire span from Cs to Sr . - I see this information on the right tab of the span as ‘Relative Time’ under the ‘Server Start’ annotation. But the actual span does not show the duration bar.
Using 2.21 version of zipkin with inmemory storage and java brave client library.
Am I missing anything, or is this the expected behaviour?