Problem
After generating traffic for your AWS Lambda function and waiting five minutes, none of your function data appears in the New Relic UI. There aren't any errors in the logs, and no NRIntegrationErrors or NRIntegrationWarnings in the New Relic UI.
Solution
The most common reason for no data appearing and no errors is that the license key and account ID are from different accounts. In the case of a mismatch, the New Relic Lambda extension or lambda that processes cloud watch logs does report the data successfully, but silently drops it since the account ID doesn't match. This results in no errors or warnings.
To resolve this issue, make sure that the license key and account ID are from the same account. Using the New Relic Lambda CLI to enable serverless monitoring is recommended to minimize these types of issues. You can update the license key in the AWS Secrets Manager. For the account ID and configurations not using the AWS Secrets Manager, you can update the environment variables with the correct license key or account ID to correct the problem.