Distributed tracing with Camunda 7 and New Relic

We’re using Camunda 7 and new relic. When trying to enable distributed tracing, we need to set the transaction context to the same key. We’re currently using the business key as the key to correlate all transactions.

In Camunda, when we’re approaching the async continuation; it creates a job for the sequent execution and is handled in a separate thread. How do I set the context (business key as a custom attribute) for the background thread that’s handling the async task?

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.