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
I need to customize a span right after its creation and before its activation (injecting some baggage items).
I am encountering this need for both regular Servlet based applications and WebFlux applications.
In the Servlet world, it’s totally feasible thanks to a ServletFilterSpanDecorator.onRequest() which is invoked right after the span creation and before its activation.
See TracingFilter.
However, it’s not achievable in the reactor world as the WebFluxSpanDecorator.onRequest() is actually called at the subscription time occurring after the span activation.
See TracingOperator and TracingSubscriber.
Could we extend the WebFluxSpanDecorator by adding a new callback onCreate() that would be called right after the span creation?
I would also remove This is called right after span in created from the onRequest()documentation as it's not really the case.
Let me know if you agree with the proposal, I'll be happy to contribute! :)
The text was updated successfully, but these errors were encountered:
Hello!
I need to customize a span right after its creation and before its activation (injecting some baggage items).
I am encountering this need for both regular Servlet based applications and WebFlux applications.
In the Servlet world, it’s totally feasible thanks to a
ServletFilterSpanDecorator.onRequest()
which is invoked right after the span creation and before its activation.See TracingFilter.
However, it’s not achievable in the reactor world as the
WebFluxSpanDecorator.onRequest()
is actually called at the subscription time occurring after the span activation.See TracingOperator and TracingSubscriber.
Could we extend the
WebFluxSpanDecorator
by adding a new callbackonCreate()
that would be called right after the span creation?I would also remove
This is called right after span in created
from theonRequest()
documentation as it's not really the case.Let me know if you agree with the proposal, I'll be happy to contribute! :)
The text was updated successfully, but these errors were encountered: