nodejs 14 lambda log duration over 120 seconds about newrelic-lambda-extension HOT 6 OPEN

We have another similar report to this. It's a very difficult issue for us to reproduce, but we want to get to the bottom of it. We are having a hard time getting to the root cause with the information we have at the moment.

from newrelic-lambda-extension.

@xuetaofeng how frequently does this happen, and how frequently does your lambda function invoke? We believe this is some kind of race condition in high frequency lambda functions.

from newrelic-lambda-extension.

@xuetaofeng Are you setting the handler correctly? If not, this will cause a timeout. What is your handler set to? The handler must be set to newrelic-lambda-wrapper.handler which is a wrapped handler that is built into the .Net layer. https://docs.newrelic.com/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/instrument-your-own/

from newrelic-lambda-extension.

@iamemilio Running into this too but can't set the handler due to using ES Modules and following the guidelines here: https://github.com/newrelic/newrelic-lambda-layers/blob/993944fd0c8b6e6592672689f22aa744bffa752c/README.md#support-for-es-modules-nodejs

Any advice?

On deploying your function, don't set the function handler to our Node wrapper; instead, use your regular handler function, which you've wrapped with newrelic.setLambdaHandler().

from newrelic-lambda-extension.

@xuetaofeng are you using the pg postgres library? or MiddyJS?

from newrelic-lambda-extension.

Running into the same issue with Node14.x and pg + MiddyJS setup. Is there an example on how to handle lambda code with pg and middy library?

from newrelic-lambda-extension.