Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lambda is showing http request as separated context #1002

Open
ciolial opened this issue Nov 22, 2024 · 0 comments
Open

Lambda is showing http request as separated context #1002

ciolial opened this issue Nov 22, 2024 · 0 comments

Comments

@ciolial
Copy link

ciolial commented Nov 22, 2024

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.
Screenshot 2024-11-22 095452
Screenshot 2024-11-22 095507
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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant