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

Support using the Agent as a layer on AWS Lambda #6

Open
willarmiros opened this issue Nov 27, 2019 · 3 comments
Open

Support using the Agent as a layer on AWS Lambda #6

willarmiros opened this issue Nov 27, 2019 · 3 comments
Labels
enhancement New feature or request

Comments

@willarmiros
Copy link
Contributor

willarmiros commented Nov 27, 2019

When adding the AWS X-Ray Java Agent to a Lambda function via a layer it causes cold starts to be much (30+ seconds) slower. This increase is so dramatic that it is a blocker for having official Lambda support. This is a result of the initialization work the agent must do to auto-instrument your Lambda code, and appears to be a problem with all auto-instrumentation java agents on the Lambda platform. An investigation is needed with the Lambda team to resolve this.

@willarmiros willarmiros added the enhancement New feature or request label Nov 3, 2020
@srprash
Copy link
Contributor

srprash commented Nov 9, 2020

The sample app link is broken. :)

@willarmiros
Copy link
Contributor Author

Thanks, it was pointing to the old (beta) sample app.

@willarmiros willarmiros changed the title Agent causes slow cold start times on AWS Lambda Support using the Agent as a layer on AWS Lambda Nov 10, 2020
@adrian-baker
Copy link

Agent causes slow cold start times on AWS Lambda

I think the old title is still accurate, enabling the agent on my lambda took the cold start time from about 10 seconds to 100.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants