Distributed tracing for RestEasy Reactive

[michalszynkiewicz]

With RestEasy Classic we can trace the calls with Jaeger, we need the same functionality for RestEasy Reactive, both for server and client (client needs to propagate appropriate headers)

[quarkus-bot]

/cc @FroMage, @Ladicek, @geoand, @kenfinnigan, @stuartwdouglas

[kenfinnigan]

I kind of have this covered as part of #17118 as well.

I know today the Reactive REST Client bit isn't there, but there should be tracing with OpenTelemetry for RESTEasy Reactive server components.

[michalszynkiewicz]

Should we close this then and add a bullet about the client to #17118 ?

[kenfinnigan]

Thinking on it more, I think it's ok for this to be open, as I know there is work needed for the client which can be added under this issue instead of the validation one.

I think I'd planned on creating issues when I find things during validation, but I know the client is missing for reactive, so this can stay

[kenfinnigan]

Today I've verified the server tracing is working for RESTEasy Reactive.

It's only the client missing

[michalszynkiewicz]

@kenfinnigan do you intend to work on it? Or should I?

[kenfinnigan]

I wouldn't be getting to it until some time next week at the earliest. If you have the time it would be appreciated

[michalszynkiewicz]

I doubt I will have time for this that soon too :) If I do, I will let you know