If you are running into an issue with New Relic Lambda and would like Support to troubleshoot, it will likely require us to review the Lambda logs for the function in question. Here’s a quick way to copy and upload that logging information!
- Invoke the function in AWS Lambda
- Click on the
logslink after your function runs:
Execution result: succeeded(logs) <-- click on this link
This will take you to the logs in AWS. On the left sidebar in AWS, under Logs, click on Insights.
Select your function and also the newrelic-log-ingestion stream
- Apply an appropriate Time Filter (depending on when the issue occurred), and a log entry limit (the default of 20 may not be enough):
- Under Actions select Copy query results (ASCII)
- Paste the text into a new .txt file; save and upload the file to the ticket.
Note that the NR_LAMBDA_MONITORING payload contains all the information the agent wants to send up, including metrics, events, some AWS account metadata, invocations and errors data. Keep in mind that some of that data (for example, New Relic legacy metrics) will not make it to NR One because our ingest pipeline does not consume them.