You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This library does not support UDP communication between client and agent. Client is connecting directly to jaeger collector via gRPC. Agent are circumvented totally and are not needed any more in the jaeger architecture. How is this good? And why does Jaeger documentation, helm chart etc. still say to use agents if they can not be accessed using the new client?
And in the end it doesn't event work. I tried to use open telemetry client and I get this error bellow when starting the microservice that is using it:
│ # A fatal error has been detected by the Java Runtime Environment: │
│ # │
│ # SIGSEGV (0xb) at pc=0x0000000000003efe, pid=1, tid=0x00007fc9a087cae8 │
│ # │
│ # JRE version: OpenJDK Runtime Environment (8.0_171-b11) (build 1.8.0_171-b11) │
│ # Java VM: OpenJDK 64-Bit Server VM (25.171-b11 mixed mode linux-amd64 compressed oops) │
│ # Derivative: IcedTea 3.8.0 │
│ # Distribution: Custom build (Wed Jun 13 18:28:11 UTC 2018) │
│ # Problematic frame: │
│ # C 0x0000000000003efe │
│ # │
│ # Core dump written. Default location: /xxxxx/core or core.1 │
│ # │
│ # An error report file with more information is saved as: │
│ # /xxxxx/hs_err_pid1.log │
│ # │
│ # If you would like to submit a bug report, please include │
│ # instructions on how to reproduce the bug and visit: │
│ # http://icedtea.classpath.org/bugzilla │
│ #
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I know this is connected to java jaeger-client but please read this post because I can't find information anywhere.
I says in java jaeger client readme https://github.com/jaegertracing/jaeger-client-java that jaeger-client library is being deprecated and open telemetry library should be used instead.
I followed this suggested guide https://medium.com/jaegertracing/migrating-from-jaeger-client-to-opentelemetry-sdk-bd337d796759
to implement the new open telemetry client (with latest versions of boms).
Why and how is open telemetry library with jaeger bridge considered ready?
This library does not support UDP communication between client and agent. Client is connecting directly to jaeger collector via gRPC. Agent are circumvented totally and are not needed any more in the jaeger architecture. How is this good? And why does Jaeger documentation, helm chart etc. still say to use agents if they can not be accessed using the new client?
And in the end it doesn't event work. I tried to use open telemetry client and I get this error bellow when starting the microservice that is using it:
PS.
asked the question also here: jaegertracing/jaeger-client-java#827
Beta Was this translation helpful? Give feedback.
All reactions