This is the meta issue for AWS Lambda support for different agents (starting with NodeJS, Java and Python).
The task includes:
The current Elastic APM Node.js agent is not working in AWS Lambda. While it used to work on previous versions ( There seems to be some digging by the Elastic team, see https://github.com/elastic/apm-agent-nodejs/issues/827 | Summary: | | Agent | AWS Lambda support |Status
|
|---|---|
| SPEC issue: |聽|
|---|---:|
| Java |
|
| NodeJS |
|
| Python |
|
We would like to have AWS Lambda-django in Elastic APM. We are able to push the CPU and memory metrics.. Also transactions are appearing in Kibana. However, APM is not showing any transactions or Errors.
Thanks for raising this!
We will include it into prioritization going forward, although it will unlikely going to be implemented in the short term.
AWS has introduced Lambda extensions:
https://aws.amazon.com/blogs/compute/introducing-aws-lambda-extensions-in-preview/
It seems it is the way to go as other vendors like Datadog, NewRelic and AppDynamics have already released extensions for it.
Thanks for the link, @nugroho-expereo! We also saw this release and this is definitely the route we intend to take with our support.
Is there any type of idea when this is going to be looked at? We really would love to use this over xray/datadog in our Lambdas.
Most helpful comment
Is there any type of idea when this is going to be looked at? We really would love to use this over xray/datadog in our Lambdas.