-
Notifications
You must be signed in to change notification settings - Fork 600
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
Explore options for AWS Lambda instrumentation #2364
Labels
Milestone
Comments
kford-newrelic
added this to the Ruby Agent - Serverless support for AWS Lambda milestone
Dec 14, 2023
kford-newrelic
added
2
Story Point Estimate
jan-mar qtr
Possible FY Q4 candidate
labels
Dec 14, 2023
kford-newrelic
changed the title
[Spike] Explore options for AWS Lambda instrumentation
Explore options for AWS Lambda instrumentation
Dec 20, 2023
Here's where we're at currently for alignment with the existing NR Lambda spec: Complete
In Progress
|
All agent work is now ready for review with 2474. Other NR repos for Lambda and documentation will still need to be updated. |
The original scope of this one has been satisfied. We're code complete and will track testing, documentation, and updates to relevant CI/CD repos separately with other issues. |
github-project-automation
bot
moved this from In Sprint
to Code Complete/Done
in Ruby Engineering Board
Mar 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Intention is that we provide the ability to instrument AWS Lambda functions. Need to identify the best way to achieve that; is it using the existing Ruby agent - perhaps in
lite
mode? Some other component?Acceptance Criteria
Design Consideration/Limitations
N/A
Dependencies
TBD
Additional context
Research spike. After determining what's feasible, we should identify the work needed in the future.
The text was updated successfully, but these errors were encountered: