Codeless Agent 3.5.4 - Multiple requests are getting combined at child HTTP process instead of parent Parent HTTP flow

[abhikt48]

Expected behavior

Every request should have End To End Transaction details, which should include parent and child process details.

Actual behavior

If we submit multiple requests (4-5 @ same time ) on parent HTTP listener which internally triggers child HTTP flow, then ETE of Parent flow does not have souce child details. surprisingly, one child HTTP request ETE contains multiple sources, which doesn't looks right.

We want to know,

1. why multiple entries attached with one child HTTP request ?
2. Why Parent and child requests are not tied together in ETE transaction.

In blow Flow, we can see parent HTTP flow is calling sub HTTP request

ETE Of Parent HTTP

ETE Of Child HTTP where we can see multiple source entry and multiple child entries as well.

NOTE - We are tesing this feature with Mule.

[trask]

hi @abhikt48, can you create a repro for this one also? if we are successful and testing with Mule in #3736, then we can take a look at this also

overall though, Mule is difficult for us to test and support (and we haven't heard of either of these issues occurring outside of Mule), so if you can test this with the upstream OpenTelemetry Java agent to see if the same issue exists, it would be great if you could debug the issue and propose a solution in the OpenTelemetry Java agent

[abhikt48]

Hey @trask Thanks for quick reply. I have created mule-app-insights-test repo and added steps.

Please do test and let me know for any query.

On another Note - We have more than 120 mule applications which are using Azure AI. It will be greate if you can do POC and take a look on our use cases with AI..

Thanks for support !

[asos-radhikajoshi]

Hi @trask , Please let us know if there is any update on this issue. Thanks, Radhika

[zoomingrocket]

We leverage in similar use case with Boomi, and native request correlation works properly. Ensure that between the two Mule APIs you have W3C Trace Headers configured in your API definition, as those will be automatically inserted by the App Insight Java Agent, and that is crucial for automatic request span distributed coorelation W3C Trace HTTP Headers - https://www.w3.org/TR/trace-context/#trace-context-http-headers-format