Is this a new feature, an improvement, or a change to existing functionality?

New Feature

How would you describe the priority of this feature request

Critical (currently preventing usage)

Please provide a clear description of problem this feature solves

We try to integrate NAT to our own framework for observability. Our framework works natively in a multi-process : we allow agents not only implemented through different framework to interact with each other, but as well agents running on different python environments.

To simplify our use case, let's assume that I have 2 workflows, A and B, serving endpoints (through routes) that expose agent A_1 and B_1. In that case, I'll be able to operate agent A_1 and B_1 independantly through each workflow, and algorithmically build a global trace for a workflow A_1 -> B_1.

I would like to know if there could be a possibility to propagate observability from workflow A to expose the detail coming from workflow B natively, instead of having observability over workflow B, and especially the detail of B_1 execution, being "black-boxed" at the workflow A level.

Describe your ideal solution

Our current system passes to each remote call an obsevability ID used to merge spans over different systems.
Another solution could be to use internal/specific routes from the workflow to expose detail traces for it to be collected by the first workflow at some point

Additional context

No response

Code of Conduct

• I agree to follow this project's Code of Conduct
• I have searched the open feature requests and have found no duplicates for this feature request