-
Notifications
You must be signed in to change notification settings - Fork 754
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
OpenTelemetry example missing root span #1743
Comments
Have you managed to solve this issue? |
Having the same issue, root span is never emitted to the collector. |
I have the same issue: it works fine when using otel's stdout exporter, but the root span is missing when using an |
This is somewhat resolved by #2110—the core issue is that the root span in the example is closed after the collector shuts down due to drop rules. |
It seems so. However, this feels like a very sneaky pitfall that one might not consider in a scenario where the root span is opened on application start-up, and should perhaps be mentioned in the documentation. I'm willing to close this issue either way; just putting the idea out there. |
Bug Report
Version
Current Git HEAD: 500021c
Platform
Linux redacted 5.12.18-1-ck-haswell #1 SMP PREEMPT Mon, 19 Jul 2021 10:10:38 +0000 x86_64 GNU/Linux
Crates
tracing-opentelemetry, examples
Description
When trying the example in the
tracing-opentelemetry
README, the span data that arrives in Jaeger is missing the rootapp_start
span.In an attempt to make sure it wasn't my fault, I tried both stable and nightly rustc, as well as the
latest
tag for Jaeger and various numbered releases. However, I don't really have any experience with OpenTelemetry in general, so I don't really know what else I might be doing wrong.To check if this was maybe a Jaeger issue, I replaced the Jaeger exporter with a pretty-print stdout exporter to inspect the data generated, and got this:
As you can see, the root
app_start
span is missing from the output.The text was updated successfully, but these errors were encountered: