WebClient Observation does not propagate context #29339
Labels
in: web
Issues in web modules (web, webmvc, webflux, websocket)
status: superseded
An issue that has been superseded by another
theme: observability
An issue related to observability and tracing
type: bug
A general bug
currently the
DefaultWebClient
is first starting the observation and only after we start it do we set the carrier on the context. That leads to not setting any trace related headers on the carrier (because there's no carrier at the start of the Observation).Also, we should be checking whether there's a parent observation in the Reactor Context before we start the observation for the WebClient call
The text was updated successfully, but these errors were encountered: