Comments (11)
Hi @jeremiahlukus. I'm a maintainer for the New Relic Ruby agent. I've developed quite a bit with AWS Lambda myself and would certainly love to help with any initiative that sees New Relic offer ever-improving value to Rubyists.
While we do not currently have any plans to share for Lambda Ruby support, GitHub issues like this one and comments left on it like yours definitely help us gauge interest and build proposals. Thank you for reaching out.
AWS Lambda itself did not originally offer support for Ruby, and New Relic's support for AWS Lambda seems consistent with the language runtimes AWS originally offered. With Ruby support now available from AWS, the Rubyists at New Relic discuss and consider instrumenting it alongside the myriad other priorities being evaluated for other Ruby use cases. And of course in addition to AWS adding support for Ruby, other cloud providers have continually been iterating on their serverless offerings as well and we look at those too.
For the benefit of any observers for this issue, the New Relic Ruby agent offers 2 key alternatives to waiting on official first party support for functionality:
- Ruby devs can wire up their own custom instrumentation within their apps
- All New Relic open source code repositories welcome pull requests
Thanks again for giving the Ruby team some fresh curiosity in this matter that we can surface.
from newrelic-lambda-layers.
@jeremiahlukus That would be driven by the Ruby agent team--they'd be doing instrumentation for Lambda functions in Ruby. Let me ping them for more background. (This plugin's aimed at deployment, so while it could be added, there would need to be a compatible layer for installing the agent.)
from newrelic-lambda-layers.
We have released layers for Ruby 3.3 & 3.2 runtimes. Please use layers website to get the latest ARN for the Ruby layers. Thanks @fallwith
from newrelic-lambda-layers.
https://issues.newrelic.com/browse/NR-142162
from newrelic-lambda-layers.
@mrickard Hey do you know if this is being worked on or considered?
from newrelic-lambda-layers.
Greate thank you, i just realized that this issue should probably be in https://github.com/newrelic/newrelic-lambda-layers , should i post a new issue there?
from newrelic-lambda-layers.
@jeremiahlukus I can transfer it. The Ruby team would still be the best ones to answer--they're aware of your question now, too.
from newrelic-lambda-layers.
Great thank you for looking into this and pinging the right people, youβre awesome π.
from newrelic-lambda-layers.
Bump having this would be great.
from newrelic-lambda-layers.
We will release support for Ruby. PR will be merged after testing.
from newrelic-lambda-layers.
https://new-relic.atlassian.net/browse/NR-266787
from newrelic-lambda-layers.
Related Issues (20)
- lambda layer: drop node 14 HOT 1
- Layer is a resource hog, requiring a large amount of memory for acceptable cold start HOT 40
- Stop publishing Node 14 layers
- NR node lambda layer doesn't initialize function when using Provisioned Concurrency & fails to find handler when exported within promise HOT 3
- Java 21 Layer HOT 1
- Reduce boilerplate for build and publish scripts
- Large slowdowns in Python cold start times HOT 4
- When NewRelic is down, the lambda (nodejs) falls in timeout and emits a slow response HOT 4
- Node lambda layer tries to access SSM for license key HOT 1
- Newrelic instrumented lambdas are failing with /lib64/libc.so.6: version `GLIBC_2.34' not found HOT 1
- Visibility into the Lambda layer version in New Relic HOT 1
- Migrate CircleCI jobs to GHA
- Investigate if NR lambda layer sequence is important for successful instrumentation HOT 2
- Update the test dependencies for Python and restore the more recent runtimes HOT 1
- Unable to use New Relic layer in lambda that is already using the aws-lambda-web-adapter layer HOT 1
- Issue with dotnet layer publishing workflow HOT 3
- Missing entity name for lambda logs HOT 5
- Remove Node 16 from layer publishing immediately before the Node agent drops 16 support HOT 3
- Supported runtimes for the extension layer HOT 1
- Missing entity name for lambda logs HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. πππ
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from newrelic-lambda-layers.