Replies: 1 comment 3 replies
-
There is no such thing as "end of trace". Trace is just a collection of spans. If Jaeger Backend shows timeline beyond the end of the last span, that is its bug. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
If you see the below image of a Trace timeline, the trace stays open and empty long after the microservices flow has ended.
Note: I am using OTEL java instrumentation to generate the traces, and feeding them to a Jaegar Backend
Is there a way for us to close the Trace once we understand that an execution flow is complete and Jaegar/OpenTelemetry should not wait for any more spans to be generated?
Beta Was this translation helpful? Give feedback.
All reactions