-
Notifications
You must be signed in to change notification settings - Fork 210
Description
Expected behavior
I would expect to see the trace of the event with all the requests that I make using my Executors.newWorkStealingPool.
I even tried to perform context wrapping with the OpenTelemetry task wrapping, but nothing works the, Mongo DB access which is executed in threadpool stays in a completely separated trace, which makes the traces a bit useless in terms of tracking.
var es = Context.taskWrapping(Executors.newWorkStealingPool(2));
Actual behavior
Mongo DB access which is executed in threadpool (with a submit) stays in a completely separated trace, which makes the traces a bit useless in terms of tracking.
To Reproduce
Receive an event from Kafka for example and perform a mongo db/cosmos query in a workstealling threadpool.
Sample Application
If applicable, provide a sample application which reproduces the issue.
System information
Please provide the following information:
- SDK Version: 3.2.11 and 3.3.0
- OS type and version: Windows 11
- Application Server type and version (if applicable):
- Using spring-boot? 2.6.4
- Additional relevant libraries (with version, if applicable):
Logs
Screenshots
Mongo traces appear like this alone.
