We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There are plans to support Java Reactor with this model of context-propagation?
Reactor implements reactive-streams specification.
Regads
The text was updated successfully, but these errors were encountered:
Hi,
Not right now, but if you want to provide support via a PR, we could add it.
Sorry, something went wrong.
Came here to find out how to implement this when using reactor together with quarkus. Just that the next person has it a bit easier in the future: It seems to be enough for reactor to work with quarkus if you follow advice in https://github.com/opentracing-contrib/java-reactor#non-agent-configuration
It boils down getting an io.opentracing.Tracer tracer injected and run this once on startup of your application:
io.opentracing.Tracer tracer
Hooks.onEachOperator(TracedSubscriber.asOperator(tracer)) Hooks.onLastOperator(TracedSubscriber.asOperator(tracer))
Tested in JVM & native mode. I'm unsure whether it eats kittens along the way, but I do get trace IDs propagated this way.
No branches or pull requests
There are plans to support Java Reactor with this model of context-propagation?
Reactor implements reactive-streams specification.
Regads
The text was updated successfully, but these errors were encountered: