Skip to content
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

Closed
ctron opened this issue Jul 1, 2020 · 13 comments · Fixed by #10405
Closed

Field jaeger.version is empty when using quarkus-jaeger #10399

ctron opened this issue Jul 1, 2020 · 13 comments · Fixed by #10405
Labels
kind/bug Something isn't working
Milestone

Comments

@ctron
Copy link
Contributor

ctron commented Jul 1, 2020

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:

  1. Using qauarkus-jaeger

Screenshots

image

Environment (please complete the following information):

$ uname -a
Linux brocken 5.6.19-300.fc32.x86_64 #1 SMP Wed Jun 17 16:10:48 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
$ java -version
openjdk version "11.0.7" 2020-04-14
OpenJDK Runtime Environment 18.9 (build 11.0.7+10)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.7+10, mixed mode, sharing)
  • 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 or gradlew --version):

    Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
    Maven home: /home/jreimann/tools/maven/apache-maven-current
    Java version: 11.0.7, vendor: Oracle Corporation, runtime: /usr/lib/jvm/java-11-openjdk-11.0.7.10-1.fc32.x86_64
    Default locale: en_US, platform encoding: UTF-8
    OS name: "linux", version: "5.6.19-300.fc32.x86_64", arch: "amd64", family: "unix"
    

Additional context
(Add any other context about the problem here.)

@ctron ctron added the kind/bug Something isn't working label Jul 1, 2020
@geoand
Copy link
Contributor

geoand commented Jul 1, 2020

cc @pavolloffay

@pavolloffay
Copy link
Contributor

This should be set to the version of the Jaeger client library.

@geoand
Copy link
Contributor

geoand commented Jul 1, 2020

Shouldn't that be done automatically?

@pavolloffay
Copy link
Contributor

it should, there is bug in jaeger client or quarkus.

@geoand
Copy link
Contributor

geoand commented Jul 1, 2020

Do you plan to look into it @pavolloffay ?

@ctron
Copy link
Contributor Author

ctron commented Jul 1, 2020

I think this is the root cause:

package io.quarkus.jaeger.runtime.graal;
import com.oracle.svm.core.annotate.Substitute;
import com.oracle.svm.core.annotate.TargetClass;
@TargetClass(className = "io.jaegertracing.internal.JaegerTracer")
public final class Target_JaegerTracer {
@Substitute
private static String loadVersion() {
// TODO: Obtain Jaeger version
return "";
}
}

@geoand
Copy link
Contributor

geoand commented Jul 1, 2020

@ctron oh... so this happens only in native mode?

@pavolloffay
Copy link
Contributor

io.jaegertracing.client.Version.get() returns correct version for Jaeger 0.34.0 that is used in Quarkus.

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?

@geoand
Copy link
Contributor

geoand commented Jul 1, 2020

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

@geoand
Copy link
Contributor

geoand commented Jul 1, 2020

I have a fix, let me just write a quick test so we can be sure this doesn't break in the future

@geoand
Copy link
Contributor

geoand commented Jul 1, 2020

#10405 should fix the issue

geoand added a commit to geoand/quarkus that referenced this issue Jul 1, 2020
@ctron
Copy link
Contributor Author

ctron commented Jul 1, 2020

@ctron oh... so this happens only in native mode?

Indeed, sorry. I forgot to mention that.

@geoand
Copy link
Contributor

geoand commented Jul 1, 2020

No worries, I found out easily via testing.

geoand added a commit to geoand/quarkus that referenced this issue Jul 1, 2020
@geoand geoand changed the title Field jaeger.version is empty when using quarkus-jaeger Field jaeger.version is empty when using quarkus-jaeger Jul 1, 2020
gsmet pushed a commit to geoand/quarkus that referenced this issue Jul 1, 2020
gsmet added a commit that referenced this issue Jul 1, 2020
Fix missing Jaeger client version in native mode
gsmet pushed a commit to gsmet/quarkus that referenced this issue Jul 1, 2020
@gsmet gsmet added this to the 1.6.0.Final milestone Jul 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants