Trask Stalnaker 05471b053b Webflux instrumentation fix (#7251) ... When a webflux filter is added which throws an exception, the instrumentation does not currently capture the `http.status_code`. The fix is to move `WebClientTracingFilter` from the first to the last filter in the chain, which I think(?) is the general strategy we've taken for other client instrumentation, e.g. so that if a filter makes another http call it won't be suppressed. I don't love the test coverage I added, so let me know if you have any better suggestions? EDIT: btw, I did archaeology to confirm that behavior (adding to the beginning of the chain) has been in place since the webflux instrumentation was added originally 6f472a62a0 (diff-493ad89b5bde807c90387aa2bb67eb10d3bcef6b6a388bd31e11796a6d01ac38R36)		2022-11-22 15:09:22 -08:00
..
main	Webflux instrumentation fix (#7251)	2022-11-22 15:09:22 -08:00
misc	Introduce markdown lint check (#7175)	2022-11-16 20:48:42 -08:00
test/java/io/opentelemetry/instrumentation	Remove old TraceUtils and use InstrumentationTestRunner#run*Span() (almost) everywhere (#5160)	2022-01-18 13:42:53 -08:00