-
Notifications
You must be signed in to change notification settings - Fork 561
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
Helidon tracing spans are not appearing in traces when used in combination with otel span via Helidon open telemetry in MP application #8892
Comments
@tjquinno can you please take a look at this ticket . |
This is reproducible even on Helidon version 4.0.10 |
There might be some issues with your reproducer steps.
|
I don't remember any of these messages appearing when I started the sample application. |
FYI, I was running Jaeger locally using the following command : |
I have started the sample application and verified that none of the SEVERE log messages you have observed are present in my case. |
Complete logs here : |
It looks as if you are now facing an OTel configuration issue, not a Helidon one. The Helidon OTel-related code ( You configure OpenTelemetry settings following the OTel documentation: https://opentelemetry.io/docs/languages/java/configuration/ You need to set as either a Java system property or an environment variable |
Helidon tracing spans are not appearing in traces when used in combination with otel span via Helidon open telemetry
Environment Details
Problem Description
We have created a Helidon MP application that uses a combination of otel spans and helidon tracing spans in a REST service. When the service execution is completed, we only see otel spans but not the Helidon tracing spans in the traces. I see that Tracer.global is returning a NoOpTracer in this case.
I will attach the sample application to reproduce the problem.
Steps to reproduce
helidon-quickstart-mp.zip
The text was updated successfully, but these errors were encountered: