Lambda is showing http request as separated context

[ciolial]

Hi,
Sorry to open a blank issue but I don't know which issue type to choose.
I've manually instrumented a .net lambda function and an aspnet api which call a step function which in turn invokes the lambda.
So the flow is: api -> sf -> lambda -> other http calls.
I see the traces correctly on x-ray but the last part of the flow is represented separately on the map.


I attached the screenshot to represent better the situation. In the first one we see the link from step function and the lambda (the step function is not instrumented, it might be retrieved from the instrumented api that calls it). And then in the last one we see the lambda, with the custom service name that I configured in the code, that calls the other services. I was expecting to see these links from the first screenshot where we see the lambda called by step function.
Where could be the issue here?

Thanks

[serkan-ozal]

Hi @ciolial, as far as I see, you have some trace link issues with AWS XRay, right? If so, this shouldn't be OTEL issue.

[ciolial]

Hi @serkan-ozal, thanks for the reply. I am a newbie on OTEL, so it could be. I've opened an AWS support case too.
Let's see what they will answer.In the meantime I saw the OTEL_PROPAGATORS environment variable which has as default value “tracecontext,baggage”. It supports xray as well.. It might be related to that or some other env vars to set?