Opentelemetry for Kogito Workflows

[tech-bee-10]

Description

I have created Kogito Workflow which involved AsyncAPI operators using Kafka for publishing and subscribing. I have integrated Opentelemetry following this doc: https://quarkus.io/guides/opentelemetry#cdi

What is happening is, when the workflow transitions from one step to another, the tracing context is not being carried forward and it uses different context at different steps. It would be good to have option to have same tracing context throughout the workflow which makes it easy to track the full execution flow traces using same trace_id.

Implementation ideas

No response

[radtriste]

@fjtirado @cristianonicolai

[fjtirado]

@rand-guy sorry for the delay on taking a look into this.
The tracing context is not the same one once the workflow is resumed after receiving an event?
Can you provide a simple reproducer to be sure we address the same issue?