AWS Lambda monitoring integration

Access to this feature depends on your subscription level.

New Relic Infrastructure's integrations include an integration for reporting your AWS Lambda data to New Relic products. This document explains how to activate this integration and describes the data that can be reported.


AWS Lambda is a zero-administration compute platform for back-end web developers that runs your code for you in the AWS cloud and provides you with a fine-grained pricing structure.

New Relic's AWS Lambda integration reports data such as invocation counts, error counts, function timers, and other metrics and metadata. You can view your Lambda data in pre-built dashboards and also create custom queries and charts in New Relic Insights.

Activate integration

To enable this integration, follow the instructions in Connect AWS services to Infrastructure.

Polling frequency

Polling information for the AWS Lambda integration:

  • New Relic polling interval: 5 minutes
  • Amazon CloudWatch data interval: 1 minute

Find and use data

To find your integration data in Infrastructure, go to > Integrations > Amazon Web Services and select one of the Lambda integration links.

In New Relic Insights, data is attached to the ServerlessSample event type, with provider values of LambdaFunction, LambdaFunctionAlias, and LambdaEventSourceMapping.

For more on how to use your data, see Understand and use integration data.

Metric data

This integration collects the following metrics. For more on these metrics, see Amazon's Lambda documentation.

Name Description
Measures the number of times a function is invoked in response to an event or invocation API call. This replaces the deprecated RequestCount metric. This includes successful and failed invocations, but does not include throttled attempts. This equals the billed requests for the function. Note that AWS Lambda only sends these metrics to CloudWatch if they have a nonzero value.

Measures the number of invocations that failed due to errors in the function (response code 4XX). This replaces the deprecated ErrorCount metric. Failed invocations may trigger a retry attempt that succeeds. This includes:

  • Handled exceptions (for example,
  • Unhandled exceptions causing the code to exit
  • Out of memory exceptions
  • Timeouts
  • Permissions errors

This does not include invocations that fail due to invocation rates exceeding default concurrent limits (error code 429) or failures due to internal service errors (error code 500).

Measures the elapsed wall clock time in milliseconds from when the function code starts executing as a result of an invocation to when it stops executing. This replaces the deprecated Latency metric. The maximum data point value possible is the function timeout configuration. The billed duration will be rounded up to the nearest 100 millisecond. Note that AWS Lambda only sends these metrics to CloudWatch if they have a nonzero value.
Measures the number of Lambda function invocation attempts that were throttled due to invocation rates exceeding the customer’s concurrent limits (error code 429). Failed invocations may trigger a retry attempt that succeeds.

Inventory data

This integration supports the following inventory data. For more about inventory data, see Understand integration data.

Name Description



Describes mapping between an Amazon Kinesis stream and a Lambda function. For full documentation on the possible values, Amazon's documentation for EventSourceMappingConfiguration.


A complex type that describes function metadata. For full documentation on the possible values, see Amazon's documentation for FunctionConfiguration.

For more help

Recommendations for learning more: