-
Notifications
You must be signed in to change notification settings - Fork 17
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
Web Client support #21
Comments
What web client do you exactly mean? |
Hi @pavolloffay, the Vert.x Web Client: That is an asynchronous HTTP and HTTP/2 client. I mean, because it is not propagated the opentracing headers to the integrations that use HTTP. |
So is there anyway to propagate the tracing in vertx 3.x? |
Vertx 3.x is problematic. This library supports only vertx-web. |
Hi, I managed to do it by passing context from route context on to vertx
context and putting everything on MDC.
If you want I can review with you my solution and it works very well.
I also created a vertx webclient interceptor that adds all the propagation
headers and allows me to fully utilize the Jaeger capabilities.
Yoni Davidson,
…On Tue, Dec 1, 2020 at 10:27 AM Pavol Loffay ***@***.***> wrote:
Vertx 3.x is problematic. This library supports only vertx-web.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#21 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABJYECXIUQLMG3QNC2OTNQTSSSSG3ANCNFSM4RNWS3XA>
.
|
There is Opentracing support for the Web Client (HTTP Client)?
The text was updated successfully, but these errors were encountered: