Containerized instrumentation

Add New Relic to your Dockerfile

New Relic offers pre-built images that include our layer's different runtimes: Java, Node.js, Python, and extension-only.

1. Select the layer compatible with your specific Lambda function's runtime and region:

   • Java
   • Node.js
   • Python
   • Ruby
   • .NET
   • Extension-only

2. In your multi-stage Dockerfile, use New Relic's prebuilt image as an intermediate build stage. Then, copy New Relic's agent and extension from our prebuilt image into your final build stage.

   Dockerfile examples based on runtime

   JavaPythonNode.jsRuby.NETExtension-only

   Java

   Python

   Node.js

   Ruby

   .NET

   Extension-only

   # Define the New Relic pre-built image
   FROM public.ecr.aws/newrelic-lambda-layers-for-docker/newrelic-lambda-layers-java:21 AS layer
   
   # Define the base image
   FROM public.ecr.aws/lambda/java:21
   
   # Copy New Relic Layer code
   COPY --from=layer /opt/ /opt/
   
   # Rest of your Dockerfile...
   
   # CMD override to one of New Relic's handler wrappers
   CMD [ "com.newrelic.java.HandlerWrapper::handleRequest" ]
   # CMD [ "com.newrelic.java.HandlerWrapper::handleStreamsRequest" ]

   Copy

   Try out working example of a Java containerized Lambda function using SAM.

   # Define the New Relic pre-built image
   FROM public.ecr.aws/newrelic-lambda-layers-for-docker/newrelic-lambda-layers-python:311 AS layer
   
   # Define the base image
   FROM public.ecr.aws/lambda/python:3.11
   
   # Copy New Relic Layer code
   COPY --from=layer /opt/ /opt/
   
   # Rest of your Dockerfile...
   
   # CMD override to New Relic's handler wrapper
   CMD [ "newrelic_lambda_wrapper.handler" ]

   Copy

   Try out working example of a Python containerized Lambda function using SAM.

   # Define the New Relic pre-built image
   FROM public.ecr.aws/newrelic-lambda-layers-for-docker/newrelic-lambda-layers-nodejs:20 AS layer
   
   # Define the base image
   FROM public.ecr.aws/lambda/nodejs:20
   
   # Copy New Relic Layer code
   COPY --from=layer /opt/ /opt/
   
   # Rest of your Dockerfile...
   
   # CMD override to New Relic's handler wrapper
   CMD [ "newrelic-lambda-wrapper.handler" ]
   # If your lambda function is ESM, use the New Relic's Node.js ESM handler wrapper
   # CMD ["/opt/nodejs/node_modules/newrelic-esm-lambda-wrapper/index.handler"]

   Copy

   Try out working example of a Node.js containerized Lambda function using SAM.

   # Define the New Relic pre-built image
   FROM public.ecr.aws/newrelic-lambda-layers-for-docker/newrelic-lambda-layers-ruby:33 AS layer
   
   # Define the base image
   FROM public.ecr.aws/lambda/ruby:3.3
   
   # Copy New Relic Layer code
   COPY --from=layer /opt/ /opt/
   
   # Rest of your Dockerfile...
   
   # CMD override to New Relic's handler wrapper
   CMD [ "newrelic_lambda_wrapper.handler" ]

   Copy

   FROM public.ecr.aws/newrelic-lambda-layers-for-docker/newrelic-lambda-layers-dotnet:x86_64 AS layer
   
   # Define the base image
   FROM public.ecr.aws/lambda/dotnet:8
   
   # Copy New Relic Layer code
   COPY --from=layer /opt/ /opt/
   
   # Rest of your Dockerfile...
   
   # CMD override not needed since the dotnet layer does not have a handler wrapper

   Copy

   FROM public.ecr.aws/newrelic-lambda-layers-for-docker/newrelic-lambda-layers-lambdaextension:x86 as layer
   
   # Any lambda base image can be used
   
   # Copy New Relic Layer code
   COPY --from=layer /opt/ /opt/
   
   # Rest of your Dockerfile...
   
   # CMD override not needed since the extension layer does not have an agent

   Copy

Create an image

1. After you add the reference to New Relic's pre-built image to your Dockerfile, you'll need to build a new image from the modified Dockerfile. This new image will have your original code and New Relic's pre-built image. To do this, we recommend following the steps listed in the AWS guide, Create a Lambda function using a container image.
2. Push the new image to your AWS Elastic Container Registry repository for your function to use.

Create a new Lambda function

Using the image you pushed to AWS ECR, create a new Lambda function. For more information on creating this function, we recommend going back to the AWS guide: Create a Lambda function.

Configure your Lambda function

2. Configure the Lambda function with the same settings as your original function, but ensure you add any required environment variables for New Relic Lambda monitoring. See our Environment variables for more information.
3. Update your function's handler to point to the newly attached layer in cmd override for your function. You can do that using the instructions in these two docs:
   • Layered instrumentation
   • SDK based instrumentation

Find and use data

After you instrument your AWS Lambda functions, you can find and use the data in the New Relic APM interface. The data is organized into several key areas, each providing different insights into the performance and health of your Lambda functions.

In the APM interface, you can explore various aspects of your Lambda functions including distributed tracing, service maps, transactions, and error analysis, and many more. Each of these areas provides detailed insights into the performance, latency, and error rates of your Lambda functions, allowing you to quickly identify and resolve issues.

To view your Lambda functions in the New Relic APM interface:

1. Go to https://one.newrelic.com > APM & Services.
2. Set the search criteria as isLambdaFunction = true.
3. From the displayed list, select your Lambda Function to view the data.