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 believe WebFilters should have auto context propagation regardless if error occurred or not.
Actual Behavior
Automatic context propagation enabled via Hooks.enableAutomaticContextPropagation(); stops working when error was being handled in WebFilter. Once error is caught, all further WebFilters are going to be stripped of MDC context.
Thanks @surmabck for the report with a reproducer.
I ran the example and here's what I observed:
If I make a request to /failing but afterwards make a request to /helloWorld then the tracing information is present in the /helloWorld handling.
My understanding is that the Observation is not attached to the reactive chain following a trigger of your WebExceptionHandler. Please report it against spring-framework.
Expected Behavior
I believe WebFilters should have auto context propagation regardless if error occurred or not.
Actual Behavior
Automatic context propagation enabled via
Hooks.enableAutomaticContextPropagation();
stops working when error was being handled in WebFilter. Once error is caught, all further WebFilters are going to be stripped of MDC context.Reproductor
I've prepared reproducer here -> https://github.com/surmabck/spring-boot-3xx-micrometer-issues/tree/only-reactor
The text was updated successfully, but these errors were encountered: