AWS Lambda Extension, sends data to NR, but does not appear in NR

Howdy

I am attempting to use the NewRelic/AWS Lambda Extension integration. I have configured my AWS account according to (https://docs.newrelic.com/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/enable-serverless-monitoring-using-lambda-layer) and I see the 3 cloudformation stacks have deployed successfully.

I then deployed the example dotnet stack here: https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/dotnet

I then navigate to the Lambda function newrelic-example-dotnet, and noticed that it is using the newrelic Layer (arn:aws:lambda:us-west-2:451483290750:layer:NewRelicLambdaExtension:3
), and invoke it with a generic test event.

In the cloudwatch logs for the invocation i see logs that look like this:

START RequestId: 8de73787-9569-4d5c-9d45-38cdb0cc8f80 Version: $LATEST
Hello, world
[NR_EXT] Sent 1/1 New Relic payload batches with 1 log events successfully in 258.239ms (257ms to transmit 1.0kB).
END RequestId: 8de73787-9569-4d5c-9d45-38cdb0cc8f80
REPORT RequestId: 8de73787-9569-4d5c-9d45-38cdb0cc8f80	Duration: 4833.98 ms	Billed Duration: 4900 ms	Memory Size: 128 MB	Max Memory Used: 103 MB	Init Duration: 347.47 ms

I then go to New Relic One and navigate to the newrelic-example-dotnet lambda function invocation, but when I click on “Distributed tracing” i see the message “we couldnt find any traces”. When i view “Cloudwatch Metrics”, I can actually see the invocations occurring. Additional when i check under Logs in NewRelic, i do not see any logs for this function.

I have also tested this with the newrelic-example-node (https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/node) example, and saw it was using Layer (arn:aws:lambda:us-west-2:451483290750:layer:NewRelicNodeJS12X:24
) and had similar Cloudwatch Logs output; however the Distributed Trace NOR Logs appear in New Relic. The cloudwatch logs in this case look like this:

LOGS Name: newrelic-lambda-extension State: Subscribed Types: [platform]

2020-11-24T21:31:44.287Z undefined INFO Lambda Handler starting up

{"v":0,"level":30,"name":"newrelic_bootstrap","hostname":"169.254.65.133","pid":15,"time":"2020-11-24T21:31:44.098Z","msg":"Cross application tracing is explicitly disabled in serverless_mode."}

{"v":0,"level":30,"name":"newrelic_bootstrap","hostname":"169.254.65.133","pid":15,"time":"2020-11-24T21:31:44.098Z","msg":"Logging is disabled by default when serverless_mode is enabled. If desired, enable logging via config file or environment variable and set filepath to a valid path for current environment, stdout or stderr."}

{"v":0,"level":30,"name":"newrelic_bootstrap","hostname":"169.254.65.133","pid":15,"time":"2020-11-24T21:31:44.098Z","msg":"The native-metrics module is disabled by default when serverless_mode is enabled. If desired, enable the native-metrics module via config file or environment variable."}

EXTENSION Name: newrelic-lambda-extension State: Ready Events: [INVOKE,SHUTDOWN]

2020-11-24T21:31:44.345Z 17b0bd71-e0c3-45d4-9406-11063febbddf INFO Hello, world

[NR_EXT] Sent 1/1 New Relic payload batches with 1 log events successfully in 198.126ms (197ms to transmit 1.3kB).

END RequestId: 17b0bd71-e0c3-45d4-9406-11063febbddf

I have also confirmed that my account has not exceeded its data usage (0 out of 100GB data ingested so far), so this does not appear to be the issue.

What else can I do do debug/resolve this issue?

Thanks for your help.

@carreseb Sorry you have been waiting awhile for a response from our community. I’m going to bring this back to the attention of our support team. Thanks for your patience!

Neal Mc

I noticed something similar right around the same time of your post…

If you haven’t already seen it, check out the solution in my thread: Problems setting up serverless monitoring / lambda layer

2 Likes

@carreseb Following up to see if the doc that @JCapriotti shared help you resolve your issue?