Merge pull request #20234 from newrelic/daily-release/03-17-25-morning

Daily release/03 17 25 morning

Author: sujitnewrelic

package.json

@@ -10,7 +10,7 @@
     "@emotion/styled": "^11.3.0",
     "@mdx-js/mdx": "2.0.0-next.8",
     "@mdx-js/react": "2.0.0-next.8",
-    "@newrelic/gatsby-theme-newrelic": "9.11.0",
+    "@newrelic/gatsby-theme-newrelic": "9.11.1",
     "@splitsoftware/splitio-react": "^1.2.4",
     "ansi-colors": "^4.1.3",
     "cockatiel": "^3.0.0-beta.0",

src/content/docs/alerts/create-alert/examples/monitor-scheduled-jobs.mdx

@@ -19,16 +19,13 @@ This technique only works for regularly scheduled jobs that occur more frequentl
 
 In order to get the most out of this procedure, you'll need to know how to [create a condition](/docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/create-alert-conditions).
 
-This only works for <DNT>**Static**</DNT> or <DNT>**Anomaly**</DNT> [threshold types](/docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/create-nrql-alert-conditions#threshold-types)..
-
 ## How it works
 
-Typically, conditions use critical thresholds to trigger incidents. However, you can also trigger incidents with a loss of signal. To monitor a scheduled job and be notified if it doesn't happen, set your condition's threshold high or low enough so that it won't trigger an incident. That way, only a loss of signal will trigger an incident.
+Typically, conditions use critical thresholds to trigger incidents. However, you can also trigger incidents with a loss of signal. To monitor a scheduled job and be notified if it doesn't happen, set your signal loss timer to match the job schedule.
 
 ## Monitor a scheduled job
 
 1. [Create a condition](/docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/create-alert-conditions) related to the job you want to monitor.
-2. In <DNT>**Set your condition thresholds**</DNT>, set the <DNT>**Critical**</DNT> threshold above or below where it would ever trigger.
-3. Click <DNT>**+ Add lost signal threshold**</DNT>, then set the signal expiration duration time longer than your monitored job's scheduled cycle.
-4. Check <DNT>**Add lost signal threshold**</DNT>.
-5. Make sure you name your condition before you save it.
+2. Click <DNT>**+ Add lost signal threshold**</DNT>, then set the signal expiration duration time longer than your monitored job's scheduled cycle.
+3. Check <DNT>**Add lost signal threshold**</DNT>.
+4. Make sure you name your condition before you save it.

src/content/docs/apis/intro-apis/new-relic-api-keys.mdx

@@ -160,9 +160,12 @@ To get started with API keys:
 
 ## View and manage API keys [#keys-ui]
 
-You can manage most API keys from the [API keys UI page](https://one.newrelic.com/api-keys) located in the [user menu](/docs/accounts/accounts-billing/general-account-settings/intro-account-settings/#user-menu) when you click <DNT>**API keys**</DNT>.
+You can manage most API keys from the [API Keys UI page](https://one.newrelic.com/api-keys) located in the [user menu](/docs/accounts/accounts-billing/general-account-settings/intro-account-settings/#user-menu) when you click <DNT>**API keys**</DNT>.
+You can also [use NerdGraph to manage keys](/docs/apis/nerdgraph/examples/use-nerdgraph-manage-license-keys-user-keys)
 
-To view a key in NerdGraph, copy the key ID.  You can also [use NerdGraph to manage keys](/docs/apis/nerdgraph/examples/use-nerdgraph-manage-license-keys-user-keys)
+During the key creation process, we temporarily provide you with the entire key. However, once the key is created, only the first 8 characters are displayed in the API Keys UI.
+
+If you need to retrieve the full key after creation, click the ellipses in the API Keys UI, copy the key ID, and [use NerdGraph to query for the full key.](/docs/apis/nerdgraph/examples/use-nerdgraph-manage-license-keys-user-keys/#query-keys).
 
 ## Recommendations for managing API keys [#security-practices]
 

src/content/docs/apm/agents/java-agent/configuration/java-agent-config-file-template.mdx

@@ -128,6 +128,19 @@ common: &default_settings
       # Default is 10000. Setting to 0 will disable.
       #max_samples_stored: 10000
 
+      # Provides the ability to add custom tags(labels) to agent forwarded logs. Labels are
+      # pulled from the top-level 'labels' section (located near the bottom of this config file).
+      # Default is false.
+      labels:
+
+        # When true, custom tags (labels) will be added to agent forwarded logs.
+        enabled: false
+
+        # A comma separated list of label keys that should NOT be added to application logs.
+        # Example:
+        #   exclude: label_name1, label_name2
+        exclude:
+
       # Whether the log events should include context from loggers with support for that.
       context_data:
 
@@ -187,11 +200,11 @@ common: &default_settings
     # When true, attributes will be sent to New Relic. The default is true.
     enabled: true
 
-    #A comma separated list of attribute keys whose values should 
+    #A comma separated list of attribute keys whose values should
     # be sent to New Relic.
     #include:
 
-    # A comma separated list of attribute keys whose values should 
+    # A comma separated list of attribute keys whose values should
     # not be sent to New Relic.
     #exclude:
 
@@ -245,7 +258,7 @@ common: &default_settings
     # Default is true.
     explain_enabled: true
 
-    # Threshold for query execution time below which query plans will 
+    # Threshold for query execution time below which query plans will
     # not be captured. Relevant only when `explain_enabled` is true.
     # Default is 0.5 seconds.
     explain_threshold: 0.5
@@ -279,7 +292,7 @@ common: &default_settings
     ignore_status_codes: 404
 
   # Transaction events are used for histograms and percentiles. Non-aggregated data is collected
-  # for each web transaction and sent to the server on harvest. 
+  # for each web transaction and sent to the server on harvest.
   transaction_events:
 
     # Set to false to disable transaction events.
@@ -346,7 +359,7 @@ common: &default_settings
   # New Relic Real User Monitoring (RUM) gives you insight into the performance real users are
   # experiencing with your website. This is accomplished by measuring the time it takes for
   # your users' browsers to download and render your web pages by injecting a small amount
-  # of JavaScript code into the header and footer of each page. 
+  # of JavaScript code into the header and footer of each page.
   browser_monitoring:
 
     # By default the agent automatically inserts API calls in compiled JSPs to
@@ -360,7 +373,7 @@ common: &default_settings
   # All instrumentation modules can be found here: https://github.com/newrelic/newrelic-java-agent/tree/main/instrumentation
   class_transformer:
 
-    # This instrumentation reports the name of the user principal returned from 
+    # This instrumentation reports the name of the user principal returned from
     # HttpServletRequest.getUserPrincipal() when servlets and filters are invoked.
     com.newrelic.instrumentation.servlet-user:
       enabled: false
@@ -394,7 +407,7 @@ common: &default_settings
     # present on the actual class, will still get named based on route and HTTP method.
     enhanced_spring_transaction_naming: false
 
-    # Actuator endpoint transaction naming 
+    # Actuator endpoint transaction naming
     # By default, built-in actuator endpoints and custom actuator endpoints (using the @Endpoint annotation
     # and its subclasses) will all be named as "OperationHandler/handle" in New Relic. Setting this
     # to true will result in the transaction name reflecting the actual base actuator endpoint URI.

src/content/docs/apm/agents/java-agent/configuration/java-agent-configuration-config-file.mdx

@@ -1542,7 +1542,7 @@ This section details the Java agent configuration options for [AI monitoring](/d
 </Callout>
 
 <Callout variant="important">
-  When enabled, AI monitoring  records a streaming copy of inputs and outputs sent to and from the models you choose to monitor, including any personal information contained therein. 
+  When enabled, AI monitoring  records a streaming copy of inputs and outputs sent to and from the models you choose to monitor, including any personal information contained therein.
   You're responsible for obtaining consent from your model users that their interactions may be recorded by a third party (New Relic) for the purpose of providing the AI monitoring feature.
 </Callout>
 
@@ -3947,6 +3947,9 @@ application_logging:
   forwarding:
     enabled: true
     max_samples_stored: 10000
+    labels:
+      enabled: false
+      exclude:
     context_data:
       enabled: false
       include:
@@ -4090,6 +4093,78 @@ If you're using a supported logging framework and want to use the agent to send
   </Collapser>
 </CollapserGroup>
 
+  #### Log labels (tags) [#log-labels]
+
+  The Java agent supports adding custom labels (tags) to agent-forwarded logs. Labels are sourced from the [labels](#labels) section at the top level of the agent configuration. This feature can be enabled within the `labels` section, nested under the `forwarding` section. You can override these settings using the `newrelic.config.application_logging.forwarding.labels` prefixed system property. Available options include:
+
+      <CollapserGroup>
+        <Collapser
+          id="cfg-application_logging_forwarding_labels"
+          title="enabled"
+        >
+          <table>
+            <tbody>
+              <tr>
+                <th>
+                  Type
+                </th>
+
+                <td>
+                  Boolean
+                </td>
+              </tr>
+
+              <tr>
+                <th>
+                  Default
+                </th>
+
+                <td>
+                  `false`
+                </td>
+              </tr>
+
+            </tbody>
+          </table>
+
+          Toggles whether the agent will add labels to logs that are forwarded to New Relic.
+      </Collapser>
+
+      <Collapser
+        id="cfg-application_logging_forwarding_labels-exclude"
+        title="exclude"
+      >
+        <table>
+          <tbody>
+            <tr>
+              <th>
+                Type
+              </th>
+
+                  <td>
+                    List of strings
+                  </td>
+                </tr>
+
+                <tr>
+                  <th>
+                    Default
+                  </th>
+
+                  <td>
+                    (none)
+                  </td>
+                </tr>
+              </tbody>
+            </table>
+
+            A case-insensitive list of label names to **exclude** when labels for logs are enabled. This attribute does not support wildcards or regex.
+      <Callout variant="important">
+        When adding labels as attributes, the agent prefixes the keys with `tags.`. This prefix is **NOT** included when matching against the exclude filtering rules.
+      </Callout>
+  </Collapser>
+</CollapserGroup>
+
 #### Log context data [#log-context-data]
 
 The Java agent can capture context data (Mapped Diagnostic Context in logback/slf4j, ThreadContext in log4j2) and add its contents as attributes in the logs forwarded to New Relic. You can control that through settings in the `context_data` section, nested under the `forwarding` section. These settings can be overridden by the `newrelic.config.application_logging.forwarding.context_data` prefixed system property. Options available are:
@@ -5343,7 +5418,7 @@ Transaction events data is used to display histograms and percentiles in the UI.
     </table>
 
     The maximum number of sampled transaction events reported every 60 seconds.
-   
+
   <Callout variant="important">
   The minimum number of sample transaction events is 12. Agents with version 5.5.0 or higher send data every 5 seconds. If you set the number of events to less than 12, the number of events sent during the harvest cycle will be insufficient, resulting in no data being sent.
   </Callout>

src/content/docs/apm/agents/java-agent/instrumentation/instrument-aws-sqs-message-queues.mdx

@@ -14,6 +14,21 @@ The Java Agent supports instrumentation for AWS SQS message queues. While our SQ
 
 To see all supported SQS libraries, refer to [Java compatibility and requirements page](/docs/agents/java-agent/getting-started/compatibility-requirements-java-agent). 
 
+<Callout variant="important">
+  Users of Java Agent 8.18.0 need to manually enable SQS instrumentation. You can enable this instrumentation in your `newrelic.yml` file:
+
+```yml
+class_transformer:
+  aws-java-sdk-sqs:
+    enabled: true
+```
+
+Alternatively, you can set the system property `-Dnewrelic.config.class_transformer.aws-java-sdk-sqs.enabled=true` or the environment variable `NEW_RELIC_CLASS_TRANSFORMER_AWS_JAVA_SDK_SQS_ENABLED=true`. 
+
+The instrumentation is enabled by default for other versions of the Java Agent. 
+
+</Callout>
+
 ## View SQS Distributed Tracing
 
 The AWS SQS SDK instrumentation automatically includes distributed trace headers as message attributes for SQS messages. This functionality is available starting from version 2.1.0. However, for message receiver operations, there isn't a built-in method to process these headers. We suggest that you implement custom instrumentation to read the distributed trace headers.

src/content/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5287.mdx

@@ -0,0 +1,13 @@
+---
+subject: Mobile app for Android
+releaseDate: '2025-03-17'
+version: 5.28.7
+downloadLink: 'https://play.google.com/store/apps/details?id=com.newrelic.rpm'
+---
+### Enhancements
+* New feature : In-App web view for quick login
+* Enhanced user analytics 
+* NR mobile agent upgrade.
+
+### Bugfixes 
+* Alert notification and global settings.

src/content/docs/security/security-privacy/compliance/certificates-standards-regulations/fedramp.mdx

@@ -207,5 +207,47 @@ The following services are not FedRAMP-authorized:
         New Relic AI
       </td>
     </tr>
+
+    <tr>
+      <td>
+        N/A
+      </td>
+
+      <td>
+        AWS
+      </td>
+
+      <td>
+        Agentic Integration - Github Copilot
+      </td>
+    </tr>
+
+    <tr>
+      <td>
+        N/A
+      </td>
+
+      <td>
+        AWS
+      </td>
+
+      <td>
+        Agentic Integration - Google Gemini Code Assist
+      </td>
+    </tr>
+
+    <tr>
+      <td>
+        N/A
+      </td>
+
+      <td>
+        AWS
+      </td>
+
+      <td>
+        Agentic Integration - Amazon Q Business
+      </td>
+    </tr>
   </tbody>
 </table>

src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/containerized-images.mdx

@@ -7,7 +7,7 @@ redirects:
 freshnessValidatedDate: never
 ---
 
-If you're using a containerized image for a Lambda function and want to monitor your application, you'll need to add a pre-built [New Relic Lambda layer](https://gallery.ecr.aws/newrelic-lambda-layers-for-docker?page=1) to your Dockerfile that matches your function's runtime. 
+If you're using a containerized image for a Lambda function and want to monitor your application, you'll need to add a pre-built [New Relic Lambda layer](https://gallery.ecr.aws/newrelic-lambda-layers-for-docker?page=1) to your Dockerfile that matches your function's runtime.
 
 Here's a diagram showing the process of adding New Relic to the Dockerfile so you can monitor your function:
 
@@ -122,6 +122,8 @@ Here's a guide to adding our pre-built layer to your code.
 
           # 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"]
           ```
           Try out [working example](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/sam/containerized-lambda/nodejs-sam-example) of a Node.js containerized Lambda function using SAM.
         </TabsPageItem>

src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda.mdx

@@ -73,7 +73,7 @@ Based on your runtime, you can set the following environment variables to furthe
             <td>`NEW_RELIC_USE_ESM`</td>
             <td>`false`</td>
             <td>`true`, `false`</td>
-            <td>**Required**: Enable ESM functions that use async/await and not callbacks by setting this to `true`</td>
+            <td>**DEPRECATED**: This will be removed from future versions of the Node.js lambda layer.  Instead set your handler to `/opt/nodejs/node_modules/newrelic-esm-lambda-wrapper/index.handler`</td>
         </tr>
         <tr>
             <td>`NODE_OPTIONS`</td>
@@ -293,7 +293,7 @@ You can find more environment variables in our [Python configuration documentati
             <td>`/opt/lib/newrelic-dotnet-agent/libNewRelicProfiler.so`</td>
             <td>**Required**: Set this to `/opt/lib/newrelic-dotnet-agent/libNewRelicProfiler.so` to enable the .NET agent</td>
         </tr>
-        
+
         <tr>
             <td>`NEW_RELIC_DISTRIBUTED_TRACING_ENABLED`</td>
             <td>`true`</td>
@@ -411,7 +411,7 @@ See more environment variables for the New Relic extension in our [documentation
     </TabsPageItem>
 
 
-    </TabsPages>    
+    </TabsPages>
 </Tabs>
 
 ## What's next

src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx

@@ -158,7 +158,7 @@ Depending on your needs, you can choose to either bypass the extension and only
         // Add latest New Relic Lambda layer ARN from https://layers.newrelic-external.com
         const NewReliclayerArn = 'arn:aws:lambda:us-east-1:451483290750:layer:NewRelicNodeJS20X:39';
         const myFunction = new lambda.Function(this, "NewRelicExampleLambda", {
-          runtime: lambda.Runtime.NODEJS_20_X, 
+          runtime: lambda.Runtime.NODEJS_20_X,
           // Update functions handler to point to the New Relic Lambda wrapper
           handler: "newrelic-lambda-wrapper.handler",
           code: lambda.Code.fromAsset('lib/lambda-runtime-code'),
@@ -226,7 +226,9 @@ Depending on your needs, you can choose to either bypass the extension and only
       * `RequestHandler` implementation: `com.newrelic.java.HandlerWrapper::handleRequest`.
       * `RequestStreamHandlerWrapper` implementation: `com.newrelic.java.HandlerWrapper::handleStreamsRequest`.
     * Python: `newrelic_lambda_wrapper.handler` (underscores).
-    * Node: `newrelic-lambda-wrapper.handler` (hyphens).
+    * Node:
+      * CommonJS: `newrelic-lambda-wrapper.handler` (hyphens).
+      * ESM: `/opt/nodejs/node_modules/newrelic-esm-lambda-wrapper/index.handler` (hyphens).
     * For .Net you don't have to set the handler.
 
     Note that for Go, you must make source code changes to your Lambda function to instrument it. Configuration changes are not enough.
@@ -263,4 +265,4 @@ Depending on your needs, you can choose to either bypass the extension and only
   <DocTile title="Compatibility and requirement" path="/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/compatibility-requirement-lambda-monitoring">Learn more about supported runtimes and prerequisites</DocTile>
   <DocTile title="Data and UI" path="/docs/serverless-function-monitoring/aws-lambda-monitoring/ui-data/understand-lambda-monitoring-ui/" >Learn how to use New Relic to monitor your AWS Lambda functions</DocTile>
   <DocTile title="Troubleshooting" path="/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting" >Learn how to troubleshoot installation related issues</DocTile>
-</DocTiles>
+</DocTiles>

src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-enabling-serverless-monitoring-aws-lambda.mdx

@@ -31,7 +31,7 @@ Besides these basic enablement problems, there are some additional problems that
 
   * If you're instrumenting with layers: make sure in your function configuration that the New Relic layer is merged before other layers (though if your function uses webpack, the New Relic layer should be merged after the webpack layer).
   * If you're instrumenting a Node.js function manually, make sure that [logging is enabled](/docs/apm/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration/#logging_config), and that your function imports <DNT>**newrelic**</DNT> before it imports any dependencies you expect to monitor.
-  * If you're using ES Modules with a Node.js function, make sure that the environment variable `NEW_RELIC_USE_ESM` is set to `true`. Additionally, make sure you're using async/await or promises for handling asynchronous behavior in your function, as callback-based functions are not supported when using ES Modules.
+  * If you're using ES Modules with a Node.js function, make sure to change the handler function to `/opt/nodejs/node_modules/newrelic-esm-lambda-wrapper/index.handler`. Additionally, set the environment variable of `NODE_PATH` to `--experimental-loader newrelic/esm-loader.mjs`.
 
 If none of these solutions help you, contact our [support team](https://support.newrelic.com/). The following information will help you when you talk to support technicians: