Skip to content

nodejs spans not exported when upgrading aws otel lambda layer to 1.15.0 #669

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.

Sign up for GitHub

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

Jump to bottom
Closed
umarkhan17 opened this issue Aug 10, 2023 · 7 comments
Closed

nodejs spans not exported when upgrading aws otel lambda layer to 1.15.0 #669

umarkhan17 opened this issue Aug 10, 2023 · 7 comments
Labels
stale

Comments

@umarkhan17
Copy link

When we use layer arn:......:aws-otel-nodejs-amd64-ver-1-0-1:2 we are able to see the spans being exported, but when we use lambda layer arn:.......:aws-otel-nodejs-amd64-ver-1-15-0:1 we are able to see the spans being exported.

We are using manual instrumentation.
@umarkhan17
Copy link
Author

We are using node 18.x runtimes. Layers till version 1-7-0:1 or 2 works, anything after that just simply does not work.
Is node 18.x runtime not officially supported by the layer?

@vasireddy99
Copy link
Contributor

vasireddy99 commented Aug 14, 2023 •
edited
Loading

Thanks for creating the issue, Can you provide more information on :aws-otel-nodejs-amd64-ver-1-0-1:2and 1-7-0:1/2 is working on nodejs18.x runtime. but :aws-otel-nodejs-amd64-ver-1-15-0:1 is not working on nodejs18.x runtime? or Is the question that the layer works on other runtimes nodejs16.x etc., but didn't work on nodejs18.x runtime?

@umarkhan17
Copy link
Author

The layer after 1-7-0 didn’t work on either of the nodejs runtimes.

@umarkhan17
Copy link
Author

umarkhan17 commented Aug 14, 2023 •
edited
Loading

The collector runs, but i do not see any spans being generated on console(console span exporter). I have verified this by using both auto & manual instrumentation, so the problem is not with the collector, but with the instrumentation, am i doing anything wrong?

@nicognaW
Copy link

I'm having the same problem with aws-otel-nodejs-amd64-ver-1-15-0:2 and runtime nodejs18.x, I haven't tested any other versions of the layer or the runtime. I posted the issue here aws-observability/aws-otel-community#672.

Please let me know if you have anything want me to try.

@github-actions GitHub Actions
Copy link

This issue is stale because it has been open 90 days with no activity. If you want to keep this issue open, please just leave a comment below and auto-close will be canceled

@github-actions github-actions bot added the stale label Dec 17, 2023
@github-actions GitHub Actions
Copy link

This issue was closed because it has been marked as stale for 30 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 21, 2024
lukeina2z pushed a commit to lukeina2z/aws-otel-lambda that referenced this issue Mar 21, 2025
ensure collector version is produced by amd64 (aws-observability#669)
8e6e0c4 
Otherwise this step fails as the gh runner can't run arm64. We only need this version to be set once anyways.

Fixes aws-observability#652

Signed-off-by: Alex Boten <aboten@lightstep.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
stale
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@vasireddy99 @umarkhan17 @nicognaW