From 5308483804a7f0307bc23e3a6cbf0e14df34f3f5 Mon Sep 17 00:00:00 2001 From: cbehera-newrelic Date: Tue, 9 Jun 2026 18:42:03 +0530 Subject: [PATCH 1/5] NR-572481: Document NEW_RELIC_APP_NAME support for Lambda APM mode - Corrected NEW_RELIC_APP_NAME description in env-variables-lambda.mdx: removed "not used in the New Relic UI" across Node.js, Python, Go, .NET, and Lambda extension tabs; clarified APM mode entity grouping behavior - Added new guide: set-lambda-apm-entity-name.mdx - Added new guide: group-lambdas-single-apm-entity.mdx - Updated serverless-function-monitoring.yml nav to include both new guides Co-Authored-By: Claude Sonnet 4.6 --- .../env-variables-lambda.mdx | 14 ++- .../group-lambdas-single-apm-entity.mdx | 95 +++++++++++++++++++ .../set-lambda-apm-entity-name.mdx | 80 ++++++++++++++++ src/nav/serverless-function-monitoring.yml | 4 + 4 files changed, 189 insertions(+), 4 deletions(-) create mode 100644 src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/group-lambdas-single-apm-entity.mdx create mode 100644 src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/set-lambda-apm-entity-name.mdx diff --git a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda.mdx b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda.mdx index abb4c5493d4..2b479622449 100644 --- a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda.mdx +++ b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda.mdx @@ -109,7 +109,7 @@ Based on your runtime, you can set the following environment variables to furthe `NEW_RELIC_APP_NAME` - Set the application name, though it is not used in the New Relic UI + Sets the application name for APM monitoring. When `NEW_RELIC_APM_LAMBDA_MODE` is set to `true`, this name is used as the APM entity name in the New Relic UI. Lambda functions sharing the same app name and New Relic account are grouped under a single APM entity. `NEW_RELIC_LOG_ENABLED` @@ -167,7 +167,7 @@ You can find more environment variables in our [Node.js configuration documentat `NEW_RELIC_APP_NAME` - Set the application name, though it is not used in the New Relic UI + Sets the application name for APM monitoring. When `NEW_RELIC_APM_LAMBDA_MODE` is set to `true`, this name is used as the APM entity name in the New Relic UI. Lambda functions sharing the same app name and New Relic account are grouped under a single APM entity. `NEW_RELIC_LOG` @@ -279,7 +279,7 @@ You can find more environment variables in our [Java agent configuration documen `NEW_RELIC_APP_NAME` - Set the application name, though it is not used in the New Relic UI + Sets the application name for APM monitoring. When `NEW_RELIC_APM_LAMBDA_MODE` is set to `true`, this name is used as the APM entity name in the New Relic UI. Lambda functions sharing the same app name and New Relic account are grouped under a single APM entity. `NEW_RELIC_LOG` @@ -363,7 +363,7 @@ You can find more environment variables in our [Java agent configuration documen `NEW_RELIC_APP_NAME` - Set the application name, though it is not used in the New Relic UI + Sets the application name for APM monitoring. When `NEW_RELIC_APM_LAMBDA_MODE` is set to `true`, this name is used as the APM entity name in the New Relic UI. Lambda functions sharing the same app name and New Relic account are grouped under a single APM entity. `NEW_RELIC_LOG_ENABLED` @@ -399,6 +399,12 @@ You can find more environment variables in our [.NET configuration documentation + + `NEW_RELIC_APP_NAME` + + + Sets the application name used when `NEW_RELIC_APM_LAMBDA_MODE` is enabled. The extension uses this value as the APM entity name during the cold-start connect call. Lambda functions sharing the same app name and New Relic account are grouped under a single APM entity in the New Relic UI. + `NEW_RELIC_LAMBDA_EXTENSION_ENABLED` `true` diff --git a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/group-lambdas-single-apm-entity.mdx b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/group-lambdas-single-apm-entity.mdx new file mode 100644 index 00000000000..869d3ef187f --- /dev/null +++ b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/group-lambdas-single-apm-entity.mdx @@ -0,0 +1,95 @@ +--- +title: Group Lambda functions under one APM entity +metaDescription: Learn how to use NEW_RELIC_APP_NAME to group multiple Lambda functions under a single APM entity in New Relic. +freshnessValidatedDate: never +--- + +When `NEW_RELIC_APM_LAMBDA_MODE` is enabled, you can group multiple Lambda functions into a single APM entity by giving them the same `NEW_RELIC_APP_NAME`. This is useful when you have related functions—such as different handlers for the same service—that you want to monitor as a unified application. + +## How entity grouping works + +New Relic creates a single APM entity for all Lambda functions that share: + +- The same `NEW_RELIC_APP_NAME` value +- The same New Relic account +- The same runtime language + +Functions deployed across multiple AWS regions are grouped under the same entity, as long as they report to the same New Relic account. To distinguish between individual functions within a grouped entity, filter by `tags.aws.arn` in your NRQL queries. + + +Cross-runtime grouping is not supported. For example, Python and Node.js Lambda functions with the same `NEW_RELIC_APP_NAME` create separate APM entities, one per runtime. + + +## Prerequisites + +- Lambda functions instrumented with New Relic +- `NEW_RELIC_APM_LAMBDA_MODE` set to `true` on each function +- New Relic Lambda layer version that supports APM mode. See [compatibility and requirements](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/compatibility-requirement-lambda-monitoring/). + +## Set up entity grouping + +Set the same `NEW_RELIC_APP_NAME` on each Lambda function you want to group: + +```ini +NEW_RELIC_APM_LAMBDA_MODE=true +NEW_RELIC_APP_NAME=my-order-service +``` + +You can configure this using any of these methods: + + + + 1. Open your Lambda function in the AWS Management Console. + 2. Go to **Configuration > Environment variables**. + 3. Add `NEW_RELIC_APP_NAME` with your chosen entity name. + 4. Repeat for each function you want to group. + + + + ```bash + aws lambda update-function-configuration \ + --function-name YOUR_FUNCTION_NAME \ + --environment "Variables={NEW_RELIC_APM_LAMBDA_MODE=true,NEW_RELIC_APP_NAME=my-order-service}" + ``` + + + + ```hcl + resource "aws_lambda_function" "my_function" { + # ... other configuration ... + environment { + variables = { + NEW_RELIC_APM_LAMBDA_MODE = "true" + NEW_RELIC_APP_NAME = "my-order-service" + } + } + } + ``` + + + +## Verify the grouping + +After deploying your Lambda functions, trigger each function to generate a cold start. The APM entity appears in New Relic within a few minutes. + +To verify your functions are grouped: + +1. Go to **[one.newrelic.com](https://one.newrelic.com) > APM & Services**. +2. Search for the value you set in `NEW_RELIC_APP_NAME`. +3. Confirm that data from all grouped functions appears under this single entity. + +To distinguish between individual functions within the grouped entity, use NRQL with `tags.aws.arn`: + +```sql +SELECT average(duration) FROM Transaction +WHERE appName = 'my-order-service' +FACET tags.aws.arn +``` + +## Related articles + + + Learn how to set a descriptive APM entity name for a Lambda function + Reference for all Lambda environment variables including NEW_RELIC_APP_NAME + Learn how to upgrade your Lambda functions to APM monitoring + diff --git a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/set-lambda-apm-entity-name.mdx b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/set-lambda-apm-entity-name.mdx new file mode 100644 index 00000000000..f50102a27ad --- /dev/null +++ b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/set-lambda-apm-entity-name.mdx @@ -0,0 +1,80 @@ +--- +title: Set a custom name for a Lambda APM entity +metaDescription: Learn how to use NEW_RELIC_APP_NAME to set a custom display name for your Lambda function in the New Relic APM UI. +freshnessValidatedDate: never +--- + +When `NEW_RELIC_APM_LAMBDA_MODE` is enabled, the `NEW_RELIC_APP_NAME` environment variable sets the name of your Lambda function's APM entity in the New Relic UI. Without this variable, New Relic uses the Lambda function name as the entity name. + +Setting a custom name is useful when you want to: + +- Use a more descriptive or human-readable name in the APM UI +- Follow a consistent naming convention across your organization +- Group related functions under a meaningful service name. See [Group Lambda functions under one APM entity](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/group-lambdas-single-apm-entity/). + +## Prerequisites + +- Lambda function instrumented with New Relic +- `NEW_RELIC_APM_LAMBDA_MODE` set to `true` + +## Set the entity name + +Add `NEW_RELIC_APP_NAME` to your Lambda function's environment variables: + +```ini +NEW_RELIC_APM_LAMBDA_MODE=true +NEW_RELIC_APP_NAME=Payment Processing Service +``` + +You can set this using any of these methods: + + + + 1. Open your Lambda function in the AWS Management Console. + 2. Go to **Configuration > Environment variables**. + 3. Add `NEW_RELIC_APP_NAME` with your chosen name. + 4. Deploy your function to apply the changes. + + + + ```bash + aws lambda update-function-configuration \ + --function-name YOUR_FUNCTION_NAME \ + --environment "Variables={NEW_RELIC_APM_LAMBDA_MODE=true,NEW_RELIC_APP_NAME=Payment Processing Service}" + ``` + + + + ```hcl + resource "aws_lambda_function" "my_function" { + # ... other configuration ... + environment { + variables = { + NEW_RELIC_APM_LAMBDA_MODE = "true" + NEW_RELIC_APP_NAME = "Payment Processing Service" + } + } + } + ``` + + + +## Find your entity in New Relic + +After the next cold start, your Lambda function appears under the new name in the APM UI: + +1. Go to **[one.newrelic.com](https://one.newrelic.com) > APM & Services**. +2. Search for the name you set in `NEW_RELIC_APP_NAME`. +3. Select the entity to view performance data. + + +Changing `NEW_RELIC_APP_NAME` creates a new APM entity. Historical data from the previous entity name is not migrated to the new entity. The old entity remains in New Relic until it ages out of the [entity lifecycle](/docs/new-relic-solutions/new-relic-one/core-concepts/what-entity-new-relic/#entity-lifecycle). + + +## Related articles + + + Learn how to group multiple Lambda functions under a single APM entity + Reference for all Lambda environment variables + Learn how to upgrade your Lambda functions to APM monitoring + diff --git a/src/nav/serverless-function-monitoring.yml b/src/nav/serverless-function-monitoring.yml index 3866c7a8c9e..95a151463c0 100644 --- a/src/nav/serverless-function-monitoring.yml +++ b/src/nav/serverless-function-monitoring.yml @@ -15,6 +15,10 @@ pages: # path: /docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/configure-serverless-aws-monitoring - title: Upgrade to APM experience path: /docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/upgrade-to-apm-experience + - title: Set a custom name for a Lambda APM entity + path: /docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/set-lambda-apm-entity-name + - title: Group Lambda functions under one APM entity + path: /docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/group-lambdas-single-apm-entity - title: Environment variables path: /docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda - title: Layered instrumentation From e023b85e221b457bb442e0cf90e7ca616ee7a420 Mon Sep 17 00:00:00 2001 From: cbehera-newrelic Date: Tue, 9 Jun 2026 19:16:18 +0530 Subject: [PATCH 2/5] Rewrite intro of set-lambda-apm-entity-name with value proposition Replaced the feature description with a problem/solution narrative: explains entity sprawl (10 functions = 10 entities), the monitoring overhead it causes, and how NEW_RELIC_APP_NAME resolves it. Added the non-Lambda unification use case from the engineering demo. Co-Authored-By: Claude Sonnet 4.6 --- .../set-lambda-apm-entity-name.mdx | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/set-lambda-apm-entity-name.mdx b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/set-lambda-apm-entity-name.mdx index f50102a27ad..895d19e619b 100644 --- a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/set-lambda-apm-entity-name.mdx +++ b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/set-lambda-apm-entity-name.mdx @@ -4,13 +4,13 @@ metaDescription: Learn how to use NEW_RELIC_APP_NAME to set a custom display nam freshnessValidatedDate: never --- -When `NEW_RELIC_APM_LAMBDA_MODE` is enabled, the `NEW_RELIC_APP_NAME` environment variable sets the name of your Lambda function's APM entity in the New Relic UI. Without this variable, New Relic uses the Lambda function name as the entity name. +By default, New Relic creates a separate APM entity for each Lambda function, named after the function itself. If you have many functions, this quickly leads to entity sprawl—10 functions become 10 entities, each with its own summary, transactions, and error views. Jumping between them to get a complete picture of your service is tedious and time-consuming. -Setting a custom name is useful when you want to: +`NEW_RELIC_APP_NAME` solves this by letting you assign a meaningful service name to your Lambda function. When `NEW_RELIC_APM_LAMBDA_MODE` is enabled, New Relic uses this name as the APM entity name instead of the function name. All transactions, errors, distributed traces, and performance data appear under a single, recognizable entity—making it far easier to monitor and troubleshoot your serverless workloads. -- Use a more descriptive or human-readable name in the APM UI -- Follow a consistent naming convention across your organization -- Group related functions under a meaningful service name. See [Group Lambda functions under one APM entity](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/group-lambdas-single-apm-entity/). +You can also use `NEW_RELIC_APP_NAME` to unify Lambda functions with non-Lambda applications. For example, if a Python service and a Python Lambda function share the same app name and New Relic account, their data is reported to the same APM entity. You can then distinguish between them using hostname or ARN filters in your NRQL queries. + +To group multiple Lambda functions under one entity using a shared app name, see [Group Lambda functions under one APM entity](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/group-lambdas-single-apm-entity/). ## Prerequisites From 9e1f6fe8688f6add76abb56b39ad0998ff73662d Mon Sep 17 00:00:00 2001 From: cbehera-newrelic Date: Tue, 9 Jun 2026 19:27:08 +0530 Subject: [PATCH 3/5] NR-572481: Consolidate NEW_RELIC_APP_NAME docs into env-variables page MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Removed thin how-to guides (set-lambda-apm-entity-name.mdx and group-lambdas-single-apm-entity.mdx) — the procedure was just setting one env var, not enough to justify standalone pages. Moved all behavioral detail into the NEW_RELIC_APP_NAME table entries in env-variables-lambda.mdx: entity grouping rules, cross-runtime limitation, ARN filtering tip, and entity lifecycle warning. Updated nav to remove the two deleted pages. Co-Authored-By: Claude Sonnet 4.6 --- .../env-variables-lambda.mdx | 55 ++++++++++- .../group-lambdas-single-apm-entity.mdx | 95 ------------------- .../set-lambda-apm-entity-name.mdx | 80 ---------------- src/nav/serverless-function-monitoring.yml | 4 - 4 files changed, 50 insertions(+), 184 deletions(-) delete mode 100644 src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/group-lambdas-single-apm-entity.mdx delete mode 100644 src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/set-lambda-apm-entity-name.mdx diff --git a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda.mdx b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda.mdx index 2b479622449..c9ac1fb8a9e 100644 --- a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda.mdx +++ b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda.mdx @@ -109,7 +109,16 @@ Based on your runtime, you can set the following environment variables to furthe `NEW_RELIC_APP_NAME` - Sets the application name for APM monitoring. When `NEW_RELIC_APM_LAMBDA_MODE` is set to `true`, this name is used as the APM entity name in the New Relic UI. Lambda functions sharing the same app name and New Relic account are grouped under a single APM entity. + + Sets the application name used as the APM entity name in the New Relic UI when `NEW_RELIC_APM_LAMBDA_MODE` is `true`. +

+
    +
  • Functions sharing the same app name and New Relic account are grouped under one APM entity, including across AWS regions.
    • +
  • Functions of different runtimes (for example, Python and Node.js) with the same name create separate entities per runtime.
    • +
  • To distinguish individual functions within a grouped entity, filter by `tags.aws.arn` in NRQL.
    • +
  • Changing this value creates a new entity; historical data is not migrated.
    • +
+ `NEW_RELIC_LOG_ENABLED` @@ -167,7 +176,16 @@ You can find more environment variables in our [Node.js configuration documentat `NEW_RELIC_APP_NAME` - Sets the application name for APM monitoring. When `NEW_RELIC_APM_LAMBDA_MODE` is set to `true`, this name is used as the APM entity name in the New Relic UI. Lambda functions sharing the same app name and New Relic account are grouped under a single APM entity. + + Sets the application name used as the APM entity name in the New Relic UI when `NEW_RELIC_APM_LAMBDA_MODE` is `true`. +

+
    +
  • Functions sharing the same app name and New Relic account are grouped under one APM entity, including across AWS regions.
    • +
  • Functions of different runtimes (for example, Python and Node.js) with the same name create separate entities per runtime.
    • +
  • To distinguish individual functions within a grouped entity, filter by `tags.aws.arn` in NRQL.
    • +
  • Changing this value creates a new entity; historical data is not migrated.
    • +
+ `NEW_RELIC_LOG` @@ -279,7 +297,16 @@ You can find more environment variables in our [Java agent configuration documen `NEW_RELIC_APP_NAME` - Sets the application name for APM monitoring. When `NEW_RELIC_APM_LAMBDA_MODE` is set to `true`, this name is used as the APM entity name in the New Relic UI. Lambda functions sharing the same app name and New Relic account are grouped under a single APM entity. + + Sets the application name used as the APM entity name in the New Relic UI when `NEW_RELIC_APM_LAMBDA_MODE` is `true`. +

+
    +
  • Functions sharing the same app name and New Relic account are grouped under one APM entity, including across AWS regions.
    • +
  • Functions of different runtimes (for example, Python and Node.js) with the same name create separate entities per runtime.
    • +
  • To distinguish individual functions within a grouped entity, filter by `tags.aws.arn` in NRQL.
    • +
  • Changing this value creates a new entity; historical data is not migrated.
    • +
+ `NEW_RELIC_LOG` @@ -363,7 +390,16 @@ You can find more environment variables in our [Java agent configuration documen `NEW_RELIC_APP_NAME` - Sets the application name for APM monitoring. When `NEW_RELIC_APM_LAMBDA_MODE` is set to `true`, this name is used as the APM entity name in the New Relic UI. Lambda functions sharing the same app name and New Relic account are grouped under a single APM entity. + + Sets the application name used as the APM entity name in the New Relic UI when `NEW_RELIC_APM_LAMBDA_MODE` is `true`. +

+
    +
  • Functions sharing the same app name and New Relic account are grouped under one APM entity, including across AWS regions.
    • +
  • Functions of different runtimes (for example, Python and Node.js) with the same name create separate entities per runtime.
    • +
  • To distinguish individual functions within a grouped entity, filter by `tags.aws.arn` in NRQL.
    • +
  • Changing this value creates a new entity; historical data is not migrated.
    • +
+ `NEW_RELIC_LOG_ENABLED` @@ -403,7 +439,16 @@ You can find more environment variables in our [.NET configuration documentation `NEW_RELIC_APP_NAME` - Sets the application name used when `NEW_RELIC_APM_LAMBDA_MODE` is enabled. The extension uses this value as the APM entity name during the cold-start connect call. Lambda functions sharing the same app name and New Relic account are grouped under a single APM entity in the New Relic UI. + + When `NEW_RELIC_APM_LAMBDA_MODE` is `true`, the extension uses this value as the APM entity name during the cold-start connect call. +

+
    +
  • Functions sharing the same app name and New Relic account are grouped under one APM entity, including across AWS regions.
    • +
  • Functions of different runtimes (for example, Python and Node.js) with the same name create separate entities per runtime.
    • +
  • To distinguish individual functions within a grouped entity, filter by `tags.aws.arn` in NRQL.
    • +
  • Changing this value creates a new entity; historical data is not migrated.
    • +
+ `NEW_RELIC_LAMBDA_EXTENSION_ENABLED` diff --git a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/group-lambdas-single-apm-entity.mdx b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/group-lambdas-single-apm-entity.mdx deleted file mode 100644 index 869d3ef187f..00000000000 --- a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/group-lambdas-single-apm-entity.mdx +++ /dev/null @@ -1,95 +0,0 @@ ---- -title: Group Lambda functions under one APM entity -metaDescription: Learn how to use NEW_RELIC_APP_NAME to group multiple Lambda functions under a single APM entity in New Relic. -freshnessValidatedDate: never ---- - -When `NEW_RELIC_APM_LAMBDA_MODE` is enabled, you can group multiple Lambda functions into a single APM entity by giving them the same `NEW_RELIC_APP_NAME`. This is useful when you have related functions—such as different handlers for the same service—that you want to monitor as a unified application. - -## How entity grouping works - -New Relic creates a single APM entity for all Lambda functions that share: - -- The same `NEW_RELIC_APP_NAME` value -- The same New Relic account -- The same runtime language - -Functions deployed across multiple AWS regions are grouped under the same entity, as long as they report to the same New Relic account. To distinguish between individual functions within a grouped entity, filter by `tags.aws.arn` in your NRQL queries. - - -Cross-runtime grouping is not supported. For example, Python and Node.js Lambda functions with the same `NEW_RELIC_APP_NAME` create separate APM entities, one per runtime. - - -## Prerequisites - -- Lambda functions instrumented with New Relic -- `NEW_RELIC_APM_LAMBDA_MODE` set to `true` on each function -- New Relic Lambda layer version that supports APM mode. See [compatibility and requirements](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/compatibility-requirement-lambda-monitoring/). - -## Set up entity grouping - -Set the same `NEW_RELIC_APP_NAME` on each Lambda function you want to group: - -```ini -NEW_RELIC_APM_LAMBDA_MODE=true -NEW_RELIC_APP_NAME=my-order-service -``` - -You can configure this using any of these methods: - - - - 1. Open your Lambda function in the AWS Management Console. - 2. Go to **Configuration > Environment variables**. - 3. Add `NEW_RELIC_APP_NAME` with your chosen entity name. - 4. Repeat for each function you want to group. - - - - ```bash - aws lambda update-function-configuration \ - --function-name YOUR_FUNCTION_NAME \ - --environment "Variables={NEW_RELIC_APM_LAMBDA_MODE=true,NEW_RELIC_APP_NAME=my-order-service}" - ``` - - - - ```hcl - resource "aws_lambda_function" "my_function" { - # ... other configuration ... - environment { - variables = { - NEW_RELIC_APM_LAMBDA_MODE = "true" - NEW_RELIC_APP_NAME = "my-order-service" - } - } - } - ``` - - - -## Verify the grouping - -After deploying your Lambda functions, trigger each function to generate a cold start. The APM entity appears in New Relic within a few minutes. - -To verify your functions are grouped: - -1. Go to **[one.newrelic.com](https://one.newrelic.com) > APM & Services**. -2. Search for the value you set in `NEW_RELIC_APP_NAME`. -3. Confirm that data from all grouped functions appears under this single entity. - -To distinguish between individual functions within the grouped entity, use NRQL with `tags.aws.arn`: - -```sql -SELECT average(duration) FROM Transaction -WHERE appName = 'my-order-service' -FACET tags.aws.arn -``` - -## Related articles - - - Learn how to set a descriptive APM entity name for a Lambda function - Reference for all Lambda environment variables including NEW_RELIC_APP_NAME - Learn how to upgrade your Lambda functions to APM monitoring - diff --git a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/set-lambda-apm-entity-name.mdx b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/set-lambda-apm-entity-name.mdx deleted file mode 100644 index 895d19e619b..00000000000 --- a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/set-lambda-apm-entity-name.mdx +++ /dev/null @@ -1,80 +0,0 @@ ---- -title: Set a custom name for a Lambda APM entity -metaDescription: Learn how to use NEW_RELIC_APP_NAME to set a custom display name for your Lambda function in the New Relic APM UI. -freshnessValidatedDate: never ---- - -By default, New Relic creates a separate APM entity for each Lambda function, named after the function itself. If you have many functions, this quickly leads to entity sprawl—10 functions become 10 entities, each with its own summary, transactions, and error views. Jumping between them to get a complete picture of your service is tedious and time-consuming. - -`NEW_RELIC_APP_NAME` solves this by letting you assign a meaningful service name to your Lambda function. When `NEW_RELIC_APM_LAMBDA_MODE` is enabled, New Relic uses this name as the APM entity name instead of the function name. All transactions, errors, distributed traces, and performance data appear under a single, recognizable entity—making it far easier to monitor and troubleshoot your serverless workloads. - -You can also use `NEW_RELIC_APP_NAME` to unify Lambda functions with non-Lambda applications. For example, if a Python service and a Python Lambda function share the same app name and New Relic account, their data is reported to the same APM entity. You can then distinguish between them using hostname or ARN filters in your NRQL queries. - -To group multiple Lambda functions under one entity using a shared app name, see [Group Lambda functions under one APM entity](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/group-lambdas-single-apm-entity/). - -## Prerequisites - -- Lambda function instrumented with New Relic -- `NEW_RELIC_APM_LAMBDA_MODE` set to `true` - -## Set the entity name - -Add `NEW_RELIC_APP_NAME` to your Lambda function's environment variables: - -```ini -NEW_RELIC_APM_LAMBDA_MODE=true -NEW_RELIC_APP_NAME=Payment Processing Service -``` - -You can set this using any of these methods: - - - - 1. Open your Lambda function in the AWS Management Console. - 2. Go to **Configuration > Environment variables**. - 3. Add `NEW_RELIC_APP_NAME` with your chosen name. - 4. Deploy your function to apply the changes. - - - - ```bash - aws lambda update-function-configuration \ - --function-name YOUR_FUNCTION_NAME \ - --environment "Variables={NEW_RELIC_APM_LAMBDA_MODE=true,NEW_RELIC_APP_NAME=Payment Processing Service}" - ``` - - - - ```hcl - resource "aws_lambda_function" "my_function" { - # ... other configuration ... - environment { - variables = { - NEW_RELIC_APM_LAMBDA_MODE = "true" - NEW_RELIC_APP_NAME = "Payment Processing Service" - } - } - } - ``` - - - -## Find your entity in New Relic - -After the next cold start, your Lambda function appears under the new name in the APM UI: - -1. Go to **[one.newrelic.com](https://one.newrelic.com) > APM & Services**. -2. Search for the name you set in `NEW_RELIC_APP_NAME`. -3. Select the entity to view performance data. - - -Changing `NEW_RELIC_APP_NAME` creates a new APM entity. Historical data from the previous entity name is not migrated to the new entity. The old entity remains in New Relic until it ages out of the [entity lifecycle](/docs/new-relic-solutions/new-relic-one/core-concepts/what-entity-new-relic/#entity-lifecycle). - - -## Related articles - - - Learn how to group multiple Lambda functions under a single APM entity - Reference for all Lambda environment variables - Learn how to upgrade your Lambda functions to APM monitoring - diff --git a/src/nav/serverless-function-monitoring.yml b/src/nav/serverless-function-monitoring.yml index 95a151463c0..3866c7a8c9e 100644 --- a/src/nav/serverless-function-monitoring.yml +++ b/src/nav/serverless-function-monitoring.yml @@ -15,10 +15,6 @@ pages: # path: /docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/configure-serverless-aws-monitoring - title: Upgrade to APM experience path: /docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/upgrade-to-apm-experience - - title: Set a custom name for a Lambda APM entity - path: /docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/set-lambda-apm-entity-name - - title: Group Lambda functions under one APM entity - path: /docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/group-lambdas-single-apm-entity - title: Environment variables path: /docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda - title: Layered instrumentation From 6d08f611993f094b2663a165e4af4db0e37d9de2 Mon Sep 17 00:00:00 2001 From: cbehera-newrelic Date: Thu, 11 Jun 2026 17:49:37 +0530 Subject: [PATCH 4/5] NR-572481: Add NEW_RELIC_APP_NAME to Java/Ruby tabs and expand descriptions with structured headings --- .../env-variables-lambda.mdx | 125 +++++++++++++----- 1 file changed, 95 insertions(+), 30 deletions(-) diff --git a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda.mdx b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda.mdx index c9ac1fb8a9e..075b157745f 100644 --- a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda.mdx +++ b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda.mdx @@ -112,12 +112,17 @@ Based on your runtime, you can set the following environment variables to furthe Sets the application name used as the APM entity name in the New Relic UI when `NEW_RELIC_APM_LAMBDA_MODE` is `true`.

-
    -
  • Functions sharing the same app name and New Relic account are grouped under one APM entity, including across AWS regions.
    • -
  • Functions of different runtimes (for example, Python and Node.js) with the same name create separate entities per runtime.
    • -
  • To distinguish individual functions within a grouped entity, filter by `tags.aws.arn` in NRQL.
    • -
  • Changing this value creates a new entity; historical data is not migrated.
    • -
+ Entity Behaviour
+ Functions sharing the same app name and New Relic account are grouped under one APM entity. If the name matches an existing APM entity (such as from a non-Lambda service), telemetry merges into that entity. Changing this value creates a new entity; historical data is not migrated. +

+ Multi-Region Reporting
+ Multiple Lambda functions across different AWS regions can share the same `NEW_RELIC_APP_NAME` and report into a single APM entity. To distinguish individual functions within the entity, filter by `tags.aws.arn` in NRQL. +

+ Cross-Runtime Reporting
+ Functions of different runtimes (for example, Python and Node.js) with the same name create separate entities per runtime. +

+ Same App Name Across Lambda and Non-Lambda Services
+ If a Lambda function and a non-Lambda APM service (for example, a traditional web app) share the same `NEW_RELIC_APP_NAME`, they report into the same APM entity. This can be intentional for a unified view of a service that runs both Lambda and server-based workloads, but may cause confusion if unintentional, since metrics, error rates, and throughput from both are combined. @@ -179,12 +184,17 @@ You can find more environment variables in our [Node.js configuration documentat Sets the application name used as the APM entity name in the New Relic UI when `NEW_RELIC_APM_LAMBDA_MODE` is `true`.

-
    -
  • Functions sharing the same app name and New Relic account are grouped under one APM entity, including across AWS regions.
    • -
  • Functions of different runtimes (for example, Python and Node.js) with the same name create separate entities per runtime.
    • -
  • To distinguish individual functions within a grouped entity, filter by `tags.aws.arn` in NRQL.
    • -
  • Changing this value creates a new entity; historical data is not migrated.
    • -
+ Entity Behaviour
+ Functions sharing the same app name and New Relic account are grouped under one APM entity. If the name matches an existing APM entity (such as from a non-Lambda service), telemetry merges into that entity. Changing this value creates a new entity; historical data is not migrated. +

+ Multi-Region Reporting
+ Multiple Lambda functions across different AWS regions can share the same `NEW_RELIC_APP_NAME` and report into a single APM entity. To distinguish individual functions within the entity, filter by `tags.aws.arn` in NRQL. +

+ Cross-Runtime Reporting
+ Functions of different runtimes (for example, Python and Node.js) with the same name create separate entities per runtime. +

+ Same App Name Across Lambda and Non-Lambda Services
+ If a Lambda function and a non-Lambda APM service (for example, a traditional web app) share the same `NEW_RELIC_APP_NAME`, they report into the same APM entity. This can be intentional for a unified view of a service that runs both Lambda and server-based workloads, but may cause confusion if unintentional, since metrics, error rates, and throughput from both are combined. @@ -271,6 +281,26 @@ You can find more environment variables in our [Python configuration documentati `true`, `false` Enable debug logging by setting this to `true` + + `NEW_RELIC_APP_NAME` + + + + Sets the application name used as the APM entity name in the New Relic UI when `NEW_RELIC_APM_LAMBDA_MODE` is `true`. +

+ Entity Behaviour
+ Functions sharing the same app name and New Relic account are grouped under one APM entity. If the name matches an existing APM entity (such as from a non-Lambda service), telemetry merges into that entity. Changing this value creates a new entity; historical data is not migrated. +

+ Multi-Region Reporting
+ Multiple Lambda functions across different AWS regions can share the same `NEW_RELIC_APP_NAME` and report into a single APM entity. To distinguish individual functions within the entity, filter by `tags.aws.arn` in NRQL. +

+ Cross-Runtime Reporting
+ Functions of different runtimes (for example, Python and Node.js) with the same name create separate entities per runtime. +

+ Same App Name Across Lambda and Non-Lambda Services
+ If a Lambda function and a non-Lambda APM service (for example, a traditional web app) share the same `NEW_RELIC_APP_NAME`, they report into the same APM entity. This can be intentional for a unified view of a service that runs both Lambda and server-based workloads, but may cause confusion if unintentional, since metrics, error rates, and throughput from both are combined. + + @@ -300,12 +330,17 @@ You can find more environment variables in our [Java agent configuration documen Sets the application name used as the APM entity name in the New Relic UI when `NEW_RELIC_APM_LAMBDA_MODE` is `true`.

-
    -
  • Functions sharing the same app name and New Relic account are grouped under one APM entity, including across AWS regions.
    • -
  • Functions of different runtimes (for example, Python and Node.js) with the same name create separate entities per runtime.
    • -
  • To distinguish individual functions within a grouped entity, filter by `tags.aws.arn` in NRQL.
    • -
  • Changing this value creates a new entity; historical data is not migrated.
    • -
+ Entity Behaviour
+ Functions sharing the same app name and New Relic account are grouped under one APM entity. If the name matches an existing APM entity (such as from a non-Lambda service), telemetry merges into that entity. Changing this value creates a new entity; historical data is not migrated. +

+ Multi-Region Reporting
+ Multiple Lambda functions across different AWS regions can share the same `NEW_RELIC_APP_NAME` and report into a single APM entity. To distinguish individual functions within the entity, filter by `tags.aws.arn` in NRQL. +

+ Cross-Runtime Reporting
+ Functions of different runtimes (for example, Python and Node.js) with the same name create separate entities per runtime. +

+ Same App Name Across Lambda and Non-Lambda Services
+ If a Lambda function and a non-Lambda APM service (for example, a traditional web app) share the same `NEW_RELIC_APP_NAME`, they report into the same APM entity. This can be intentional for a unified view of a service that runs both Lambda and server-based workloads, but may cause confusion if unintentional, since metrics, error rates, and throughput from both are combined. @@ -340,6 +375,26 @@ You can find more environment variables in our [Java agent configuration documen `true`, `false` Generate traces by enabling Distributed Tracing + + `NEW_RELIC_APP_NAME` + + + + Sets the application name used as the APM entity name in the New Relic UI when `NEW_RELIC_APM_LAMBDA_MODE` is `true`. +

+ Entity Behaviour
+ Functions sharing the same app name and New Relic account are grouped under one APM entity. If the name matches an existing APM entity (such as from a non-Lambda service), telemetry merges into that entity. Changing this value creates a new entity; historical data is not migrated. +

+ Multi-Region Reporting
+ Multiple Lambda functions across different AWS regions can share the same `NEW_RELIC_APP_NAME` and report into a single APM entity. To distinguish individual functions within the entity, filter by `tags.aws.arn` in NRQL. +

+ Cross-Runtime Reporting
+ Functions of different runtimes (for example, Python and Node.js) with the same name create separate entities per runtime. +

+ Same App Name Across Lambda and Non-Lambda Services
+ If a Lambda function and a non-Lambda APM service (for example, a traditional web app) share the same `NEW_RELIC_APP_NAME`, they report into the same APM entity. This can be intentional for a unified view of a service that runs both Lambda and server-based workloads, but may cause confusion if unintentional, since metrics, error rates, and throughput from both are combined. + + @@ -393,12 +448,17 @@ You can find more environment variables in our [Java agent configuration documen Sets the application name used as the APM entity name in the New Relic UI when `NEW_RELIC_APM_LAMBDA_MODE` is `true`.

-
    -
  • Functions sharing the same app name and New Relic account are grouped under one APM entity, including across AWS regions.
    • -
  • Functions of different runtimes (for example, Python and Node.js) with the same name create separate entities per runtime.
    • -
  • To distinguish individual functions within a grouped entity, filter by `tags.aws.arn` in NRQL.
    • -
  • Changing this value creates a new entity; historical data is not migrated.
    • -
+ Entity Behaviour
+ Functions sharing the same app name and New Relic account are grouped under one APM entity. If the name matches an existing APM entity (such as from a non-Lambda service), telemetry merges into that entity. Changing this value creates a new entity; historical data is not migrated. +

+ Multi-Region Reporting
+ Multiple Lambda functions across different AWS regions can share the same `NEW_RELIC_APP_NAME` and report into a single APM entity. To distinguish individual functions within the entity, filter by `tags.aws.arn` in NRQL. +

+ Cross-Runtime Reporting
+ Functions of different runtimes (for example, Python and Node.js) with the same name create separate entities per runtime. +

+ Same App Name Across Lambda and Non-Lambda Services
+ If a Lambda function and a non-Lambda APM service (for example, a traditional web app) share the same `NEW_RELIC_APP_NAME`, they report into the same APM entity. This can be intentional for a unified view of a service that runs both Lambda and server-based workloads, but may cause confusion if unintentional, since metrics, error rates, and throughput from both are combined. @@ -442,12 +502,17 @@ You can find more environment variables in our [.NET configuration documentation When `NEW_RELIC_APM_LAMBDA_MODE` is `true`, the extension uses this value as the APM entity name during the cold-start connect call.

-
    -
  • Functions sharing the same app name and New Relic account are grouped under one APM entity, including across AWS regions.
    • -
  • Functions of different runtimes (for example, Python and Node.js) with the same name create separate entities per runtime.
    • -
  • To distinguish individual functions within a grouped entity, filter by `tags.aws.arn` in NRQL.
    • -
  • Changing this value creates a new entity; historical data is not migrated.
    • -
+ Entity Behaviour
+ Functions sharing the same app name and New Relic account are grouped under one APM entity. If the name matches an existing APM entity (such as from a non-Lambda service), telemetry merges into that entity. Changing this value creates a new entity; historical data is not migrated. +

+ Multi-Region Reporting
+ Multiple Lambda functions across different AWS regions can share the same `NEW_RELIC_APP_NAME` and report into a single APM entity. To distinguish individual functions within the entity, filter by `tags.aws.arn` in NRQL. +

+ Cross-Runtime Reporting
+ Functions of different runtimes (for example, Python and Node.js) with the same name create separate entities per runtime. +

+ Same App Name Across Lambda and Non-Lambda Services
+ If a Lambda function and a non-Lambda APM service (for example, a traditional web app) share the same `NEW_RELIC_APP_NAME`, they report into the same APM entity. This can be intentional for a unified view of a service that runs both Lambda and server-based workloads, but may cause confusion if unintentional, since metrics, error rates, and throughput from both are combined. From 7e455d2dc11f41696ecd1a1ebd04148a56bc6236 Mon Sep 17 00:00:00 2001 From: cbehera-newrelic Date: Thu, 11 Jun 2026 17:51:51 +0530 Subject: [PATCH 5/5] NR-572481: Extract NEW_RELIC_APP_NAME detail to standalone page, link from env-variables table --- .../app-name-apm-lambda.mdx | 40 ++++++++ .../env-variables-lambda.mdx | 98 ++----------------- 2 files changed, 47 insertions(+), 91 deletions(-) create mode 100644 src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/app-name-apm-lambda.mdx diff --git a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/app-name-apm-lambda.mdx b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/app-name-apm-lambda.mdx new file mode 100644 index 00000000000..2ef1985a11f --- /dev/null +++ b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/app-name-apm-lambda.mdx @@ -0,0 +1,40 @@ +--- +title: "NEW_RELIC_APP_NAME for AWS Lambda APM mode" +metaDescription: "Understand how NEW_RELIC_APP_NAME controls APM entity grouping, multi-region reporting, cross-runtime behavior, and shared naming with non-Lambda services." +freshnessValidatedDate: never +tags: + - AWS Lambda + - APM + - Environment Variables + - Configuration +--- + +When `NEW_RELIC_APM_LAMBDA_MODE` is `true`, the `NEW_RELIC_APP_NAME` environment variable controls how your Lambda functions appear as APM entities in New Relic. This page explains the key behaviors to understand before setting this variable. + +## Entity behaviour + +Functions sharing the same `NEW_RELIC_APP_NAME` value and New Relic account are grouped under a single APM entity in the New Relic UI. + +If the name you set matches an existing APM entity — for example, one already created by a non-Lambda service — telemetry from your Lambda function merges into that entity automatically. There is no separate entity created. + + + Changing `NEW_RELIC_APP_NAME` creates a new APM entity. Historical data associated with the previous name is not migrated to the new entity. + + +## Multi-region reporting + +Multiple Lambda functions deployed across different AWS regions can share the same `NEW_RELIC_APP_NAME`. All of these functions report into a single APM entity, regardless of which region they are deployed in. + +To distinguish individual functions or region-specific deployments within the grouped entity, filter by the `tags.aws.arn` attribute in NRQL or use the tag filter bar in the entity view. + +## Cross-runtime reporting + +Lambda functions using different runtimes (for example, a Python function and a Node.js function) that share the same `NEW_RELIC_APP_NAME` create **separate** APM entities — one per runtime. The grouping does not cross runtime boundaries. + +## Same app name across Lambda and non-Lambda services + +If a Lambda function and a non-Lambda APM service (for example, a traditional web application or microservice) are both configured with the same `NEW_RELIC_APP_NAME`, they report into the **same** APM entity. + +This can be intentional: if you want a unified view of a service that runs on both Lambda and server-based infrastructure, sharing the name allows all telemetry — transactions, errors, throughput — to appear in one place. + +However, if done unintentionally, it can cause confusion. Metrics, error rates, and throughput from the Lambda function and the non-Lambda service are combined, which may make it harder to diagnose issues or understand performance independently. diff --git a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda.mdx b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda.mdx index 075b157745f..ab9f85e1017 100644 --- a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda.mdx +++ b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda.mdx @@ -110,19 +110,7 @@ Based on your runtime, you can set the following environment variables to furthe - Sets the application name used as the APM entity name in the New Relic UI when `NEW_RELIC_APM_LAMBDA_MODE` is `true`. -

- Entity Behaviour
- Functions sharing the same app name and New Relic account are grouped under one APM entity. If the name matches an existing APM entity (such as from a non-Lambda service), telemetry merges into that entity. Changing this value creates a new entity; historical data is not migrated. -

- Multi-Region Reporting
- Multiple Lambda functions across different AWS regions can share the same `NEW_RELIC_APP_NAME` and report into a single APM entity. To distinguish individual functions within the entity, filter by `tags.aws.arn` in NRQL. -

- Cross-Runtime Reporting
- Functions of different runtimes (for example, Python and Node.js) with the same name create separate entities per runtime. -

- Same App Name Across Lambda and Non-Lambda Services
- If a Lambda function and a non-Lambda APM service (for example, a traditional web app) share the same `NEW_RELIC_APP_NAME`, they report into the same APM entity. This can be intentional for a unified view of a service that runs both Lambda and server-based workloads, but may cause confusion if unintentional, since metrics, error rates, and throughput from both are combined. + Sets the application name used as the APM entity name in the New Relic UI when `NEW_RELIC_APM_LAMBDA_MODE` is `true`. See [NEW_RELIC_APP_NAME for AWS Lambda APM mode](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/app-name-apm-lambda/) for details on entity grouping, multi-region reporting, cross-runtime behaviour, and shared naming with non-Lambda services. @@ -182,19 +170,7 @@ You can find more environment variables in our [Node.js configuration documentat - Sets the application name used as the APM entity name in the New Relic UI when `NEW_RELIC_APM_LAMBDA_MODE` is `true`. -

- Entity Behaviour
- Functions sharing the same app name and New Relic account are grouped under one APM entity. If the name matches an existing APM entity (such as from a non-Lambda service), telemetry merges into that entity. Changing this value creates a new entity; historical data is not migrated. -

- Multi-Region Reporting
- Multiple Lambda functions across different AWS regions can share the same `NEW_RELIC_APP_NAME` and report into a single APM entity. To distinguish individual functions within the entity, filter by `tags.aws.arn` in NRQL. -

- Cross-Runtime Reporting
- Functions of different runtimes (for example, Python and Node.js) with the same name create separate entities per runtime. -

- Same App Name Across Lambda and Non-Lambda Services
- If a Lambda function and a non-Lambda APM service (for example, a traditional web app) share the same `NEW_RELIC_APP_NAME`, they report into the same APM entity. This can be intentional for a unified view of a service that runs both Lambda and server-based workloads, but may cause confusion if unintentional, since metrics, error rates, and throughput from both are combined. + Sets the application name used as the APM entity name in the New Relic UI when `NEW_RELIC_APM_LAMBDA_MODE` is `true`. See [NEW_RELIC_APP_NAME for AWS Lambda APM mode](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/app-name-apm-lambda/) for details on entity grouping, multi-region reporting, cross-runtime behaviour, and shared naming with non-Lambda services. @@ -286,19 +262,7 @@ You can find more environment variables in our [Python configuration documentati - Sets the application name used as the APM entity name in the New Relic UI when `NEW_RELIC_APM_LAMBDA_MODE` is `true`. -

- Entity Behaviour
- Functions sharing the same app name and New Relic account are grouped under one APM entity. If the name matches an existing APM entity (such as from a non-Lambda service), telemetry merges into that entity. Changing this value creates a new entity; historical data is not migrated. -

- Multi-Region Reporting
- Multiple Lambda functions across different AWS regions can share the same `NEW_RELIC_APP_NAME` and report into a single APM entity. To distinguish individual functions within the entity, filter by `tags.aws.arn` in NRQL. -

- Cross-Runtime Reporting
- Functions of different runtimes (for example, Python and Node.js) with the same name create separate entities per runtime. -

- Same App Name Across Lambda and Non-Lambda Services
- If a Lambda function and a non-Lambda APM service (for example, a traditional web app) share the same `NEW_RELIC_APP_NAME`, they report into the same APM entity. This can be intentional for a unified view of a service that runs both Lambda and server-based workloads, but may cause confusion if unintentional, since metrics, error rates, and throughput from both are combined. + Sets the application name used as the APM entity name in the New Relic UI when `NEW_RELIC_APM_LAMBDA_MODE` is `true`. See [NEW_RELIC_APP_NAME for AWS Lambda APM mode](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/app-name-apm-lambda/) for details on entity grouping, multi-region reporting, cross-runtime behaviour, and shared naming with non-Lambda services. @@ -328,19 +292,7 @@ You can find more environment variables in our [Java agent configuration documen - Sets the application name used as the APM entity name in the New Relic UI when `NEW_RELIC_APM_LAMBDA_MODE` is `true`. -

- Entity Behaviour
- Functions sharing the same app name and New Relic account are grouped under one APM entity. If the name matches an existing APM entity (such as from a non-Lambda service), telemetry merges into that entity. Changing this value creates a new entity; historical data is not migrated. -

- Multi-Region Reporting
- Multiple Lambda functions across different AWS regions can share the same `NEW_RELIC_APP_NAME` and report into a single APM entity. To distinguish individual functions within the entity, filter by `tags.aws.arn` in NRQL. -

- Cross-Runtime Reporting
- Functions of different runtimes (for example, Python and Node.js) with the same name create separate entities per runtime. -

- Same App Name Across Lambda and Non-Lambda Services
- If a Lambda function and a non-Lambda APM service (for example, a traditional web app) share the same `NEW_RELIC_APP_NAME`, they report into the same APM entity. This can be intentional for a unified view of a service that runs both Lambda and server-based workloads, but may cause confusion if unintentional, since metrics, error rates, and throughput from both are combined. + Sets the application name used as the APM entity name in the New Relic UI when `NEW_RELIC_APM_LAMBDA_MODE` is `true`. See [NEW_RELIC_APP_NAME for AWS Lambda APM mode](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/app-name-apm-lambda/) for details on entity grouping, multi-region reporting, cross-runtime behaviour, and shared naming with non-Lambda services. @@ -380,19 +332,7 @@ You can find more environment variables in our [Java agent configuration documen - Sets the application name used as the APM entity name in the New Relic UI when `NEW_RELIC_APM_LAMBDA_MODE` is `true`. -

- Entity Behaviour
- Functions sharing the same app name and New Relic account are grouped under one APM entity. If the name matches an existing APM entity (such as from a non-Lambda service), telemetry merges into that entity. Changing this value creates a new entity; historical data is not migrated. -

- Multi-Region Reporting
- Multiple Lambda functions across different AWS regions can share the same `NEW_RELIC_APP_NAME` and report into a single APM entity. To distinguish individual functions within the entity, filter by `tags.aws.arn` in NRQL. -

- Cross-Runtime Reporting
- Functions of different runtimes (for example, Python and Node.js) with the same name create separate entities per runtime. -

- Same App Name Across Lambda and Non-Lambda Services
- If a Lambda function and a non-Lambda APM service (for example, a traditional web app) share the same `NEW_RELIC_APP_NAME`, they report into the same APM entity. This can be intentional for a unified view of a service that runs both Lambda and server-based workloads, but may cause confusion if unintentional, since metrics, error rates, and throughput from both are combined. + Sets the application name used as the APM entity name in the New Relic UI when `NEW_RELIC_APM_LAMBDA_MODE` is `true`. See [NEW_RELIC_APP_NAME for AWS Lambda APM mode](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/app-name-apm-lambda/) for details on entity grouping, multi-region reporting, cross-runtime behaviour, and shared naming with non-Lambda services. @@ -446,19 +386,7 @@ You can find more environment variables in our [Java agent configuration documen - Sets the application name used as the APM entity name in the New Relic UI when `NEW_RELIC_APM_LAMBDA_MODE` is `true`. -

- Entity Behaviour
- Functions sharing the same app name and New Relic account are grouped under one APM entity. If the name matches an existing APM entity (such as from a non-Lambda service), telemetry merges into that entity. Changing this value creates a new entity; historical data is not migrated. -

- Multi-Region Reporting
- Multiple Lambda functions across different AWS regions can share the same `NEW_RELIC_APP_NAME` and report into a single APM entity. To distinguish individual functions within the entity, filter by `tags.aws.arn` in NRQL. -

- Cross-Runtime Reporting
- Functions of different runtimes (for example, Python and Node.js) with the same name create separate entities per runtime. -

- Same App Name Across Lambda and Non-Lambda Services
- If a Lambda function and a non-Lambda APM service (for example, a traditional web app) share the same `NEW_RELIC_APP_NAME`, they report into the same APM entity. This can be intentional for a unified view of a service that runs both Lambda and server-based workloads, but may cause confusion if unintentional, since metrics, error rates, and throughput from both are combined. + Sets the application name used as the APM entity name in the New Relic UI when `NEW_RELIC_APM_LAMBDA_MODE` is `true`. See [NEW_RELIC_APP_NAME for AWS Lambda APM mode](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/app-name-apm-lambda/) for details on entity grouping, multi-region reporting, cross-runtime behaviour, and shared naming with non-Lambda services. @@ -500,19 +428,7 @@ You can find more environment variables in our [.NET configuration documentation - When `NEW_RELIC_APM_LAMBDA_MODE` is `true`, the extension uses this value as the APM entity name during the cold-start connect call. -

- Entity Behaviour
- Functions sharing the same app name and New Relic account are grouped under one APM entity. If the name matches an existing APM entity (such as from a non-Lambda service), telemetry merges into that entity. Changing this value creates a new entity; historical data is not migrated. -

- Multi-Region Reporting
- Multiple Lambda functions across different AWS regions can share the same `NEW_RELIC_APP_NAME` and report into a single APM entity. To distinguish individual functions within the entity, filter by `tags.aws.arn` in NRQL. -

- Cross-Runtime Reporting
- Functions of different runtimes (for example, Python and Node.js) with the same name create separate entities per runtime. -

- Same App Name Across Lambda and Non-Lambda Services
- If a Lambda function and a non-Lambda APM service (for example, a traditional web app) share the same `NEW_RELIC_APP_NAME`, they report into the same APM entity. This can be intentional for a unified view of a service that runs both Lambda and server-based workloads, but may cause confusion if unintentional, since metrics, error rates, and throughput from both are combined. + When `NEW_RELIC_APM_LAMBDA_MODE` is `true`, the extension uses this value as the APM entity name during the cold-start connect call. See [NEW_RELIC_APP_NAME for AWS Lambda APM mode](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/app-name-apm-lambda/) for details on entity grouping, multi-region reporting, cross-runtime behaviour, and shared naming with non-Lambda services.