Merge pull request #23687 from newrelic/daily-merge/04-09-2026-morning

Daily merge/04 09 2026 morning

Author: sujitnewrelic

package.json

@@ -42,7 +42,7 @@
     "hast-util-to-mdast": "^7.1.3",
     "jsdom": "^16.5.0",
     "katex": "^0.16.11",
-    "lodash": "^4.17.21",
+    "lodash": "^4.18.1",
     "markdown-link-check": "^3.12.2",
     "parse-link-header": "^2.0.0",
     "prop-types": "^15.7.2",

src/content/docs/accounts/accounts/account-maintenance/account-email-settings.mdx

@@ -32,31 +32,30 @@ To ensure you get New Relic emails, you can add the following to your organizati
 
 ## Change your email address [#change-email]
 
-To change your email address: from the [user menu](/docs/accounts/accounts-billing/general-account-settings/intro-account-settings), click <DNT>**User preferences**</DNT>, and click <DNT>**Email**</DNT>.
+To change your email address: go to [<DNT>**User preferences**</DNT>](https://one.newrelic.com/user-preferences) and click <DNT>**Email**</DNT>.
 
 New Relic user email addresses have to the following restrictions:
 
 * Characters: Must be composed of letters (a-z, A-Z), numbers (0-9), and special characters `(!#$%&'*+/=?^_{|}~-)`.
 * Length: Limited to a maximum of 255 characters.
 
-<Callout variant="tip">
-  SSO/SAML users:
+### Change your email address as an SSO/SAML user [#sso-saml-email]
 
-  You can update your email address while authenticated into a SSO/SAML account using one of these methods:
+You can update your email address while authenticated into an SSO/SAML account using one of these methods:
 
-  **Option 1: User Management UI**
-  1. Navigate to [user management](https://one.newrelic.com/admin-portal/organizations/users-list)
-  2. Click into your user details.
-  3. Update your email and save.
-  4. Update your email in your identity provider to match exactly.
-  5. Test authentication.
+**User Management UI**
 
-  If you get logged out during this process and you're an admin, you can use the [one-time SSO bypass](/docs/accounts/accounts-billing/account-setup/troubleshoot-new-relics-password-email-address-login-problems/#login-troubleshooting) to regain access.
+1. Navigate to [user management](https://one.newrelic.com/admin-portal/organizations/users-list).
+2. Click into your user details.
+3. Update your email and save.
+4. Update your email in your identity provider to match exactly.
+5. Test authentication.
 
-  **Option 2: NerdGraph API**
+If you get logged out during this process and you're an admin, you can use the [one-time SSO bypass](/docs/accounts/accounts-billing/account-setup/troubleshoot-new-relics-password-email-address-login-problems/#login-troubleshooting) to regain access.
 
-  You can update your email via the [NerdGraph API](/docs/apis/nerdgraph/examples/nerdgraph-manage-users/#update-users) to avoid any risk of being logged out. For bulk updates, see this [KCS article on bulk user email updates](https://knowledge.newrelic.com/s/article/Bulk-User-Email-Updates).
-</Callout>
+**NerdGraph API**
+
+You can update your email via the [NerdGraph API](/docs/apis/nerdgraph/examples/nerdgraph-manage-users/#update-users) to avoid any risk of being logged out. For bulk updates, see this [KCS article on bulk user email updates](https://knowledge.newrelic.com/s/article/Bulk-User-Email-Updates).
 
 ## Unsubscribe from emails [#emails]
 

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

@@ -137,6 +137,11 @@ common: &default_settings
       # When true, application logs will be forwarded to New Relic. The default is true.
       enabled: true
 
+      # When true and "enable_auto_app_naming" is also true, log events will be sent
+      # to their corresponding named entity rather than the roll up entity.
+      # Default is false.
+      auto_app_naming_association: false
+
       # Application log events are collected up to the configured amount. Afterwards,
       # events are sampled to maintain an even distribution across the harvest cycle.
       # Default is 10000. Setting to 0 will disable.
@@ -153,7 +158,7 @@ common: &default_settings
         # A comma separated list of label keys that should NOT be added to application logs.
         # Example:
         #   exclude: label_name1,label_name2
-        exclude:
+        #exclude:
 
       # Whether the log events should include context from loggers with support for that.
       context_data:
@@ -167,6 +172,10 @@ common: &default_settings
         # A comma separated list of attribute keys whose values should not be sent to New Relic.
         #exclude:
 
+      # A comma separated list of strings representing log levels that should not be forwarded. Log level names are case-insensitive but otherwise must be an exact match.
+      # Example values: "info, debug"
+      #log_level_denylist:
+
     # The agent will generate metrics to indicate the number of
     # application log events occurring at each distinct log level.
     metrics:
@@ -202,6 +211,14 @@ common: &default_settings
   #proxy_password: password
   #proxy_scheme: https
 
+  # Cloud environment settings for container metadata collection:
+  # When running in containerized environments (like AWS Fargate) with a proxy,
+  # metadata endpoints may need to bypass the proxy to be accessible.
+  #cloud:
+    # Set to true to bypass proxy for cloud metadata endpoint access.
+    # Default is false.
+    #metadata_bypass_proxy: false
+
   # Limits the number of lines to capture for each stack trace.
   # Default is 30
   max_stack_trace_lines: 30
@@ -214,11 +231,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:
 
@@ -248,6 +265,22 @@ common: &default_settings
     # Default is apdex_f.
     transaction_threshold: apdex_f
 
+    # Controls the addition of comments to the beginning of executed SQL
+    # statements to be used by the New Relic Query Performance Monitoring
+    # product for entity linking. An empty String disables SQL comments
+    # (default setting).
+    # Allowed options are:
+    # nr_service_guid - The GUID of the New Relic entity this agent is instrumenting
+    # A resulting comment would resemble this:
+    # /*nr_service_guid=MTE3NDc2MDB8QVBNfEFQUExJQ0FUSU9OfDI4MTc5NDEIEA*/
+    sql_metadata_comments:
+
+    # For large SQL statements, executing the regular expressions that attempt to parse exec and
+    # call statements can take a significant amount of time. Setting this to true will disable the
+    # execution of these complex regular expressions.
+    # Default is false.
+    exec_call_sql_regex_disabled: false
+
     # When transaction tracer is on, SQL statements can optionally be
     # recorded. The recorder has three modes, "off" which sends no
     # SQL, "raw" which sends the SQL statement in its original form,
@@ -272,7 +305,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
@@ -306,7 +339,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.
@@ -388,7 +421,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
@@ -429,7 +462,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
@@ -463,6 +496,15 @@ common: &default_settings
     # present on the actual class, will still get named based on route and HTTP method.
     enhanced_spring_transaction_naming: false
 
+    # Use controller class and method for Spring transaction naming.
+    # When true, all Spring Controller transactions will be named using the controller class name
+    # and method name (e.g., "/CustomerController/edit") instead of using request mappings
+    # (e.g., "/api/v1/customer (POST)"). This setting takes precedence over enhanced_spring_transaction_naming.
+    # This helps prevent transaction name cardinality issues with complex URI patterns.
+    # Applies to Spring 4.3.x+ (spring-4.3.0 module) and Spring 6.x+ (spring-6.0.0 module).
+    # Default is false.
+    use_controller_class_and_method_for_spring_transaction_naming: false
+
     # By default, built-in actuator endpoints and custom actuator endpoints (using the @Endpoint annotation
     # and it's 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.
@@ -471,11 +513,23 @@ common: &default_settings
     # Default is false.
     name_actuator_endpoints: false
 
+  # Metric ingest URI. Determines where dimensional metric data is sent for
+  # JFR profiling. If not explicitly configured, the metric_ingest_uri
+  # will be automatically derived from the license_key (recommended).
+  #
+  # The default URI is for the US region.
+  # metric_ingest_uri: https://metric-api.newrelic.com/metric/v1
+
+  # Event ingest URI. Determines where event data is sent for
+  # JFR profiling. If not explicitly configured, the event_ingest_uri
+  # will be automatically derived from the license_key (recommended).
+  #
+  # The default URI is for the US region.
+  # event_ingest_uri: https://insights-collector.newrelic.com/v1/accounts/events
+
   # Real-time profiling using Java Flight Recorder (JFR).
-  # This feature reports dimensional metrics to the ingest endpoint configured by
-  # metric_ingest_uri and events to the ingest endpoint configured by event_ingest_uri.
-  # Both ingest endpoints default to US production but they will be automatically set to EU
-  # production when using an EU license key. Other ingest endpoints can be configured manually.
+  # This feature reports dimensional metric and event data to the endpoints
+  # configured by metric_ingest_uri and event_ingest_uri, respectively.
   # Requires a JVM that provides the JFR library.
   jfr:
 
@@ -508,6 +562,51 @@ common: &default_settings
     # An example label
     #label_name: label_value
 
+  # Telemetry signals (Logs, Metrics, and Traces) emitted by OpenTelemetry APIs can
+  # be incorporated into the Java agent and controlled by the following config options.
+  opentelemetry:
+
+    # Set to true to allow individual OpenTelemetry signals to be enabled, false to disable all OpenTelemetry signals.
+    # Default is false.
+    enabled: false
+
+    # OpenTelemetry Logs signals.
+    logs:
+
+      # Set to true to enable OpenTelemetry Logs signals.
+      # Default is true.
+      enabled: true
+
+    # OpenTelemetry Metrics signals.
+    metrics:
+
+      # Set to true to enable OpenTelemetry Metrics signals.
+      # Default is true.
+      enabled: true
+
+      # A comma-delimited string of OpenTelemetry Meters (e.g. "MeterName1,MeterName2") whose signals should be included.
+      # By default, all Meters are included. This will override any default Meter excludes in the agent, effectively re-enabling them.
+      #include:
+
+      # A comma-delimited string of OpenTelemetry Meters (e.g. "MeterName3,MeterName4") whose signals should be excluded.
+      # This takes precedence over all other includes/excludes sources, effectively disabling the listed Meters.
+      #exclude:
+
+    # OpenTelemetry Traces signals.
+    traces:
+
+      # Set to true to enable OpenTelemetry Traces signals.
+      # Default is true.
+      enabled: true
+
+      # A comma-delimited string of OpenTelemetry Tracers (e.g. "TracerName1,TracerName2") whose signals should be included.
+      # By default, all Tracers are included. This will override any default Tracer excludes in the agent, effectively re-enabling them.
+      #include:
+
+      # A comma-delimited string of OpenTelemetry Tracers (e.g. "TracerName3,TracerName4") whose signals should be excluded.
+      # This takes precedence over all other includes/excludes sources, effectively disabling the listed Tracers.
+      #exclude:
+
   # New Relic Security vulnerability detection.
   security:
     # Determines whether the security data is sent to New Relic or not. When this is disabled and agent.enabled is

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

@@ -2174,7 +2174,7 @@ common: &default_settings​
       </tbody>
     </table>
 
-    Customize the precentage of garbage collection CPU time above which the circuit breaker should trip. When the percentage of free heap memory is less than `memory_threshold`, and the CPU time spent doing garbage collection is greater than `gc_cpu_threshold`, the circuit breaker trips. In order to make the circuit breaker less likely to trip, decrease `memory_threshold` and/or increase `gc_cpu_threshold`. Adjust these values as needed, based on your application's operating performance and behavior.
+    Customize the percentage of garbage collection CPU time above which the circuit breaker should trip. When the percentage of free heap memory is less than `memory_threshold`, and the CPU time spent doing garbage collection is greater than `gc_cpu_threshold`, the circuit breaker trips. In order to make the circuit breaker less likely to trip, decrease `memory_threshold` and/or increase `gc_cpu_threshold`. Adjust these values as needed, based on your application's operating performance and behavior.
   </Collapser>
 </CollapserGroup>
 
@@ -2188,6 +2188,7 @@ An example configuration:
 cloud:
   aws:
     account_id: 123456789012
+  metadata_bypass_proxy: false
 ```
 
   <CollapserGroup>
@@ -2228,8 +2229,37 @@ cloud:
     NewRelic.getAgent().getCloud().setAccountInfo(CloudAccountInfo.AWS_ACCOUNT_ID, "...");
     ```
   </Collapser>
-</CollapserGroup>
+  <Collapser
+    id="metadata_bypass_proxy"
+    title="metadata_bypass_proxy"
+  >
+    <table>
+      <tbody>
+      <tr>
+        <th>
+          Type
+        </th>
 
+        <td>
+          Boolean
+        </td>
+      </tr>
+
+      <tr>
+        <th>
+          Default
+        </th>
+
+        <td>
+          `false`
+        </td>
+      </tr>
+      </tbody>
+    </table>
+
+    When set to true, this setting allows you to bypass proxy for cloud metadata endpoint access. Default is false.
+  </Collapser>
+</CollapserGroup>
 
 ## Cloud platform utilization [#utilization]
 
@@ -4180,6 +4210,7 @@ application_logging:
       enabled: false
       include:
       exclude:
+    log_level_denylist: debug
   metrics:
     enabled: true
   local_decorating:
@@ -4494,6 +4525,43 @@ The Java agent can capture context data (Mapped Diagnostic Context in logback/sl
   </Collapser>
 </CollapserGroup>
 
+#### Log Level Denylist [#log-level-denylist]
+
+The Java agent can omit specific log levels from generating LogEvents that get forwarded to New Relic.
+
+You can control that through the `log_level_denylist` config option, nested under the `forwarding` section. This setting allows you to define a comma separated list of strings representing log levels (e.g. `log_level_denylist: "info, debug"`) that should not have log events forwarded. Log level names are case-insensitive but otherwise must be an exact match. These settings can be overridden by the `newrelic.config.application_logging.forwarding.log_level_denylist` prefixed system property. The only available option is:
+
+<CollapserGroup>
+  <Collapser
+    id="cfg-application_logging_forwarding_log_level_denylist"
+    title="log_level_denylist"
+  >
+    <table>
+      <tbody>
+        <tr>
+          <th>
+            Type
+          </th>
+
+          <td>
+            List of strings
+          </td>
+        </tr>
+
+        <tr>
+          <th>
+            Default
+          </th>
+
+          <td>
+            (none)
+          </td>
+        </tr>
+      </tbody>
+    </table>
+  </Collapser>
+</CollapserGroup>
+
 ### Log metrics [#log-metrics]
 
 In addition to allowing you to decorate and send individual log lines, the Java agent can capture logging metric data. You can find this data in the logs chart in the New Relic UI. You can configure log metrics settings in the `metrics` section. You can override these settings with the `newrelic.config.application_logging.metrics` prefixed system property. The only available option is: