Trace context lost after mongo call

[beltram]

Bug report
Hi, using latest Spring versions (2.1.2.RELEASE and Cloud Greenwich.RELEASE) it looks like after calling mongo with reactive operators trace context is resetted (ie one cannot get back traceId). If mongo is not called it works as expected.
It looks like this:

tracer.spanId() // has a value
    .flatMap { repo.insert(Person(it)) }
    .flatMap { tracer.spanId() } // is null

Reproducer is here
Thank you 😄

[jntakpe]

Is it related to reactor/reactor-core#1481 ?

[jntakpe]

@bsideup Thoughts ?

[bsideup]

@jntakpe no, not related (the PR you linked is not integrated yet).

Looks more like a duplicate of #1203 and #1199

[jntakpe]

We have experienced the #1199. We solved it by retrieving trace information from request.

[beltram]

For information issue appeared on spring-cloud-sleuth-core:2.1.0.M2

[marcingrzejszczak]

@beltram should I just clone https://github.com/beltram/sleuth-data-reproducer and run ./gradlew clean build to replicate the problem?

[beltram]

@marcingrzejszczak sorry missed the readme on this one. Run ./gradlew clean test instead all logic is in test classes

[jntakpe]

@marcingrzejszczak any issues regarding this issue ?