-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Field jaeger.version is empty when using quarkus-jaeger #10399
Comments
cc @pavolloffay |
This should be set to the version of the Jaeger client library. |
Shouldn't that be done automatically? |
it should, there is bug in jaeger client or quarkus. |
Do you plan to look into it @pavolloffay ? |
I think this is the root cause: Lines 1 to 14 in 688ee16
|
@ctron oh... so this happens only in native mode? |
The version is obtained from properties file https://github.com/jaegertracing/jaeger-client-java/blob/release-0.34/jaeger-core/src/main/java/io/jaegertracing/internal/JaegerTracer.java#L672. The prop file should be in the jar. Can this cause any problems in Quarkus? |
Based on what @ctron posted, I am assuming the problem only occurs in native mode and that JVM mode works fine. Let me come up with a real quick fix for this so we can get it in 1.6 |
I have a fix, let me just write a quick test so we can be sure this doesn't break in the future |
#10405 should fix the issue |
Indeed, sorry. I forgot to mention that. |
No worries, I found out easily via testing. |
jaeger.version
is empty when using quarkus-jaegerFix missing Jaeger client version in native mode
Describe the bug
(Describe the problem clearly and concisely.)
The field
jaeger.version
is empty.Expected behavior
The field should contain the version of the Jaeger tracing library.
Actual behavior
The field value is empty.
To Reproduce
Steps to reproduce the behavior:
Screenshots
Environment (please complete the following information):
GraalVM version (if different from Java): 19.3.1
Quarkus version or git rev: 1.5.2.Final
Build tool (ie. output of
mvnw --version
orgradlew --version
):Additional context
(Add any other context about the problem here.)
The text was updated successfully, but these errors were encountered: