With Oneagent 1.209 came an EAP flag with support for the Reactor Netty Http Client.
We activated it for one of our processes and the calls from the reactor client are picked up now.
However they fall into the "Requests executed on a background thread of XXX" service, and not the web request service in which context the call via the reactor client is made.
I haven't found any information on the Reactor Netty Http Client in the docs or a blog. Should the link to a calling web request already work? If not is this already a known issue?
Solved! Go to Solution.
Had the same issue and after opening a support ticket it turns out that the early adopter feature "Reactor Netty Http Client" only covers the usage of reactor.netty.http.client.HttpClient. If you are using reactor core mono/flux then this tracing is currently not supported.
Thanks, I'll defiantly check that.
However the calls are picked up correctly with the flag enabled, just not linked to the incoming request. Did you have the same behavior, or no requests at all for the reactor client?
We see the requests coming in but they're identified as "background threads" and not tied to the original request - the missing support for mono/flux tracing breaks the purepath stitching.
@pahofmann there is now an RFE open for this: https://community.dynatrace.com/t5/Dynatrace-product-ideas/Support-for-Netty-Reactor-Core-Monoflux/i...
Thanks, voted for it 🙂