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

Create @sentry/profiling-node Lambda Layer #13049

Open
andreiborza opened this issue Jul 25, 2024 · 4 comments
Open

Create @sentry/profiling-node Lambda Layer #13049

andreiborza opened this issue Jul 25, 2024 · 4 comments
Assignees
Labels

Comments

@andreiborza
Copy link
Member

andreiborza commented Jul 25, 2024

As highlighted here, there are a few steps needed to successfully make use of @sentry/profiling-node in serverless environments.

While there are clear benefits to users bundling all of their code on those environments, it's a complicated process. People often use tools that abstract away low level interactions with bundlers, like AWS SAM, which makes it even harder to follow the outlined steps.

We can alleviate that by publishing an AWS Lambda layer for @sentry/profiling-node that people can add to their Lambda functions to use @sentry/profling-node out of the box.

Relevant issue: #12994
cc @JonasBa

@FredrikZeiner
Copy link

Would really like to see this. Am having issues with esbuild not copying over .node files even with '.node': 'copy', and this would solve that.

@getsantry getsantry bot moved this to Waiting for: Product Owner in GitHub Issues with 👀 3 Jan 28, 2025
@JonasBa
Copy link
Member

JonasBa commented Jan 28, 2025

@FredrikZeiner I think this may be related to some recent changes in the package that broke this. It is probably related to this issue. Would you mind downgrading the version to 8.48.0 and seeing if that is fixed?

@FredrikZeiner
Copy link

That did indeed solve it! I've been going at this for a few hours even pulling in esbuild-plugin-copy. Thank you! Sign me up still for the layer though. Am already using SentryNodeServerlessSDK.

@kieronjmckenna
Copy link

Can confirm upgrading past 8.48.0 broke functionality on lambda, even with

loader: {
    ".node": "copy",
  },

in my esbuild config

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: No status
Development

No branches or pull requests

6 participants