-
-
Notifications
You must be signed in to change notification settings - Fork 490
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
AWS lambda support #1728
Comments
Would you accept a PR adding Lambda support to I have some good experience with Lambda and we're using Sentry+Ruby+Lambda right now. |
@jordan-brough PRs are always welcome! |
@jordan-brough thanks for the offering. but can we make it under the |
yes, thought the same. |
Also for consistency, please call it |
👍 Sounds great, I'll do that. |
@sl0thentr0py this is completely up to y'all, but "serverless" is a pretty broad term within AWS, e.g. see everything they list here: Also, serverless is used beyond AWS, e.g. Azure: https://azure.microsoft.com/en-us/solutions/serverless/ So But again I don't have a stake in that so totally up to y'all! Just lmk. |
@jordan-brough you're not wrong but I was mainly thinking about consistency with our npm package naming. If we do get this ball rolling, we would also look at GCP/azure in the distant future. |
Yah that makes sense. I was wondering if you might want to chat w/ whoever maintains the node/python libraries about considering a rename on their end also. "Lambda" seems like the overall better name to me in this case. But I'll plan on (I'm assuming that a future Azure/GCP addition would probably be in a different gem/package, since I'd wager there are enough differences to merit that) |
I doubt we'll rename those libs at this point since they've been around for much longer, sry! |
Just curious, is there any movement on this 😄 ? |
@Haumer not specifically, but in the medium long term, we're working on a partially cross-language solution with the AWS Extensions API that we'll release in a couple of months for other languages. Once that is done, we'd still need to add some ruby specific code but eventually we will also use that solution in the ruby SDK. |
📝 |
For instrumenting AWS Lambda, it seems like it'd be ideal to use Lambda Extensions to deliver error reports. At first glance it looks like the
async
option would be the way to integrate with Lambda Extensions. Do any of the Sentry libraries for other languages hook into Lambda Extensions? Would there be another way to do that with the Sentry Ruby SDK?Originally posted by @jordan-brough in #1522 (comment)
The text was updated successfully, but these errors were encountered: