Hi team,
We're having issues with Trace Continuity for an application that does asynchronous processing and we're trying to explore ways to have the issue addressed so we see end-to-end traces.
With the way the application processes tasks (I'm oversimplifying here) a thread writes a statement to a DB and another thread picks it up to continue processing, but Dynatrace issues a unique Trace ID for each, so we can't see the whole transaction, end-to-end, as a single trace.
We know that OTel has a "set trace ID" function that we could use - since the original TraceID is stored in the database, but we're wondering whether enabling the OTel Span Sensor feature for OneAgent would allow us to leverage the function, or if there is any other way around it.
If any of you have ran into similar issues with Trace Continuity in Asynchronous Processing applications and could share how you handled, it would be much appreciated.
