Summary
When enabling NEW_RELIC_APM_LAMBDA_MODE=true, each Lambda function appears as an individual APM entity in New Relic. We would like the ability to group multiple Lambda functions into a single logical APM application.
Desired Behavior
New Relic should provide a mechanism to group multiple Lambda functions under one unified APM application, similar to how traditional APM agents use a shared appName to represent a single service.
This grouping would allow related Lambda functions belonging to the same serverless workflow or API to appear as one cohesive APM entity instead of fragmented individual services.
Possible Solution
- Introduce a configuration option (e.g., shared
appName, grouping key, or metadata field) that the Lambda extension can use to aggregate multiple Lambdas into one APM entity.
- Alternatively, enhance
entity.name or tagging conventions to support grouping behavior.
Additional context
Many serverless applications are composed of multiple Lambda functions that collectively form a single logical service. Having them appear individually in APM results in a scattered view, making performance analysis, troubleshooting, and Cortex integration less intuitive.
A unified APM view would significantly improve observability and streamline monitoring for serverless workflows.
Summary
When enabling
NEW_RELIC_APM_LAMBDA_MODE=true, each Lambda function appears as an individual APM entity in New Relic. We would like the ability to group multiple Lambda functions into a single logical APM application.Desired Behavior
New Relic should provide a mechanism to group multiple Lambda functions under one unified APM application, similar to how traditional APM agents use a shared
appNameto represent a single service.This grouping would allow related Lambda functions belonging to the same serverless workflow or API to appear as one cohesive APM entity instead of fragmented individual services.
Possible Solution
appName, grouping key, or metadata field) that the Lambda extension can use to aggregate multiple Lambdas into one APM entity.entity.nameor tagging conventions to support grouping behavior.Additional context
Many serverless applications are composed of multiple Lambda functions that collectively form a single logical service. Having them appear individually in APM results in a scattered view, making performance analysis, troubleshooting, and Cortex integration less intuitive.
A unified APM view would significantly improve observability and streamline monitoring for serverless workflows.