Merge branch 'newrelic:develop' into develop

Author: jcountsNR

.github/CODEOWNERS

@@ -1,21 +1,21 @@
 # .github directory & its subdirectories
-/.github/ @newrelic/docs-engineering
+/.github/ @newrelic/DOCS-ENG
 
 # Changes to yarn.lock & package.json file
-package.json @newrelic/docs-engineering
-yarn.lock @newrelic/docs-engineering
+package.json @newrelic/DOCS-ENG
+yarn.lock @newrelic/DOCS-ENG
 
 # all javascript files
-*.js @newrelic/docs-engineering
+*.js @newrelic/DOCS-ENG
 
-/plugins/ @newrelic/docs-engineering
+/plugins/ @newrelic/DOCS-ENG
 
 # .github directory & its subdirectories
-/scripts/ @newrelic/docs-engineering
+/scripts/ @newrelic/DOCS-ENG
 
 # Whats new files (pings individual project marketing managers)
 
 /src/content/whats-new/ @john-withers @aalfano7
 
 # Otel files
-/src/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/ @newrelic/opentelemetry-community
+/src/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/ @newrelic/OTELCOMM

.github/workflows/check-translations-and-deserialize.yml

@@ -77,7 +77,7 @@ jobs:
           base: develop
           delete-branch: true
           reviewers: jmiraNR
-          team-reviewers: docs-engineering
+          team-reviewers: DOCS-ENG
 
       - name: Remove Completed Batches From Queue
         if: steps.fetch-deserialize.outputs.successfulTranslations != 0 && steps.create-pr.outcome == 'success'
@@ -150,7 +150,7 @@ jobs:
           base: develop
           delete-branch: true
           reviewers: jmiraNR
-          team-reviewers: docs-engineering
+          team-reviewers: DOCS-ENG
 
       - name: Remove Completed Batches From Queue
         if: steps.fetch-deserialize.outputs.successfulTranslations != 0 && steps.create-pr.outcome == 'success'

.github/workflows/update-attribute-dictionary-json.yml

@@ -56,4 +56,4 @@ jobs:
           body: ''
           base: develop
           delete-branch: true
-          team-reviewers: docs-engineering
+          team-reviewers: DOCS-ENG

src/content/docs/accounts/accounts-billing/new-relic-one-user-management/user-permissions.mdx

@@ -104,7 +104,6 @@ To learn more about specific permissions, select a category below, or try search
   >
     These permissions pertain to [applied intelligence](/docs/alerts-applied-intelligence/applied-intelligence/incident-intelligence/get-started-incident-intelligence) features:
 
-    * <DNT>**Anomaly detection configurations**</DNT>: relates to [anomaly detection](https://docs-preview.newrelic.com/docs/expanded-anomaly-detection) (limited availability).
     * <DNT>**Channels**</DNT>: relates to [notification channels](/docs/alerts-applied-intelligence/notifications/intro-notifications).
     * <DNT>**Comments**</DNT>: relates to [postmortem comments](/docs/alerts-applied-intelligence/applied-intelligence/postmortems-applied-intelligence/#comment-event).
     * <DNT>**Destinations**</DNT>: relates to [destinations](/docs/alerts-applied-intelligence/notifications/destinations).

src/content/docs/alerts/create-alert/create-alert-condition/alert-conditions.mdx

@@ -1,18 +1,19 @@
 ---
 title: Alert conditions
 tags:
-    - Alerts
-    - Alert conditions
+  - Alerts
+  - Alert conditions
 translate:
-    - jp
+  - jp
 metaDescription: "Use the conditions page to identify what triggers an alert policy's notification, starting with the product and type of metric or service."
 redirects:
-    - /docs/alerts-applied-intelligence/new-relic-alerts/get-started/your-first-nrql-condition
-    - /docs/alerts/alert-policies/configuring-alerts/managing-your-alerts
-    - /docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/alert-conditions
-    - /docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/advanced-techniques/select-product-targets-alert-condition
-    - /docs/alerts/create-alert/create-alert-condition/create-alert-conditions
-    - /docs/alerts/create-alert/create-alert-condition/update-or-disable-policies-conditions
+  - /docs/alerts-applied-intelligence/new-relic-alerts/get-started/your-first-nrql-condition
+  - /docs/alerts/alert-policies/configuring-alerts/managing-your-alerts
+  - /docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/alert-conditions
+  - /docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/advanced-techniques/select-product-targets-alert-condition
+  - /docs/alerts/create-alert/create-alert-condition/create-alert-conditions
+  - /docs/alerts/create-alert/create-alert-condition/update-or-disable-policies-conditions
+  - /docs/alerts/new-relic-alerts-beta/configuring-alert-policies/define-alert-conditions
 freshnessValidatedDate: never
 ---
 

src/content/docs/alerts/get-notified/muting-rules-suppress-notifications.mdx

@@ -26,20 +26,20 @@ redirects:
 freshnessValidatedDate: never
 ---
 
-When the [threshold](/docs/alerts/new-relic-alerts-beta/configuring-alert-policies/define-thresholds-trigger-alert) set in a [condition](/docs/alerts/new-relic-alerts-beta/configuring-alert-policies/define-alert-conditions) is exceeded, depending on the policy's <DNT>**[Incident preference](/docs/alerts/new-relic-alerts/configuring-alert-policies/specify-when-new-relic-creates-incidents)**</DNT> settings, <InlinePopover type="alerts"/> may create an incident. You can review information about incidents in several ways:
+When the [threshold](/docs/alerts/create-alert/set-thresholds/set-thresholds-alert-condition/) set in a [condition](/docs/alerts/create-alert/create-alert-condition/alert-conditions/) is exceeded, depending on the policy's <DNT>**[Incident preference](/docs/alerts/new-relic-alerts/configuring-alert-policies/specify-when-new-relic-creates-incidents)**</DNT> settings, <InlinePopover type="alerts"/> may create an incident. You can review information about incidents in several ways:
 
 * [View the incidents index](#view-incidents) so you can scan for patterns in a list of incidents.
 * [View the incidents log](#view-log) to examine associated performance details.
-* [View the events](#incident-time) included in a specific incident to review the timestamps for [events](/docs/using-new-relic/welcome-new-relic/get-started/glossary#event), such as an incident opening or closing, notifications, and acknowledgments.
+* [View the events](#incident-time) included in a specific incident to review the timestamps for [events](/docs/using-new-relic/welcome-new-relic/get-started/glossary#event), such as an incident opening or closing, notifications, and acknowledgements.
 
 <img
-  title="screen-alerts-incident-page.png"
-  alt="screen-alerts-incident-page.png"
+  title="Incident details page"
+  alt="Incident details page"
   src="/images/alerts_screenshot-full_incident-page.webp"
 />
 
 <figcaption>
-  <DNT>**[one.newrelic.com](https://one.newrelic.com/all-capabilities) > Alerts > Incidents > (select an incident)**</DNT>: Notice that the condition's threshold was breached around 2pm (the blue line went over the red dotted line), but the alert wasn't triggered until the incident occurred for more than five minutes, as specified in the condition.
+  Go to <DNT>**[one.newrelic.com](https://one.newrelic.com/all-capabilities) > Alerts**</DNT> and click the <DNT>**Incidents**</DNT> tab. Select one of the incidents in the table to open its details.
 </figcaption>
 
 ## View the incidents index and incident details [#view-incidents]
@@ -48,14 +48,16 @@ Incidents are grouped together into incidents. If you want to change how inciden
 
 To view incident details:
 
-1. Go to <DNT>**[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Alerts > Incidents**</DNT>, then click <DNT>**Open incidents**</DNT> or <DNT>**All incidents**</DNT>.
-2. Select an incident row.
-3. Select one of the incidents to see a chart and details for it.
+1. Go to <DNT>**[one.newrelic.com](https://one.newrelic.com/all-capabilities) > Alerts**</DNT> and click the <DNT>**Incidents**</DNT> tab.
+
+2. Select one of the incidents in the table to open its details.
 
 Details for individual incident charts include:
 
 * <DNT>**Timing information**</DNT>: The shaded red area on the chart shows you the time period when the incident occurred, where the preceding shaded pink area represents the [degradation period](/docs/using-new-relic/welcome-new-relic/get-started/glossary#degradation-period). If you select an incidents that lasted longer than two hours, the timeline on the bottom of the chart will be jagged. To provide context for events in the incident, the chart also shows the time frame surrounding the incident.
+
 * <DNT>**Chart guidelines**</DNT>: The red dotted line marks the threshold for the condition. The blue line depicts performance information.
+
 * <DNT>**Anomalous behavior:**</DNT> If alerts detects [anomalous behavior](#anomalous-behavior) near the time of the incident, you'll see a notification in the incident details.
 
 From this page, you can take action regarding the incident:
@@ -84,7 +86,9 @@ From this page, you can take action regarding the incident:
       </td>
 
       <td>
-        [Acknowledge the incident](/docs/alerts/new-relic-alerts-beta/reviewing-alert-incidents/acknowledge-alert-incidents) by selecting the acknowledge <img title="Alerts v3: alert icons" alt="040815-icon-ack.webp" src="/images/alerts_icon_acknowledged.webp"/> icon or button.
+        [Acknowledge the incident](/docs/alerts/new-relic-alerts-beta/reviewing-alert-incidents/acknowledge-alert-incidents). There are 2 options: 
+        * From the selected issue row, click the <Icon name="fe-more-horizontal"/> icon and select <DNT>**Acknowledge this issue**</DNT>.
+        * From the incident details page, click the <DNT>**Acknowledge**</DNT> button.
       </td>
     </tr>
 

src/content/docs/alerts/incident-management/view-event-details-incidents.mdx

@@ -394,6 +394,15 @@ 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 
+    # 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.
+    # For example, invoking "/actuator/loggers" or "actuator/loggers/com.newrelic" will result in the
+    # transaction name "actuator/loggers (GET)". This is to prevent MGI.
+    # Default is false.
+    name_actuator_endpoints: false
+
   # 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.

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

@@ -2586,6 +2586,43 @@ Set instrumentation related settings in the `class_transformer` section. You can
     This config exists in Java agent version 8.9.0+.
   </Collapser>
 
+<Collapser
+    id="ct-name_actuator_endpoints"
+    title="name_actuator_endpoints"
+  >
+    <table>
+      <tbody>
+        <tr>
+          <th>
+            Type
+          </th>
+
+          <td>
+            Boolean
+          </td>
+        </tr>
+
+        <tr>
+          <th>
+            Default
+          </th>
+
+          <td>
+            False
+          </td>
+        </tr>
+      </tbody>
+    </table>
+
+    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. Enabling this
+setting will result in the transaction name reflecting the actual base actuator endpoint URI. For example, invoking `/actuator/loggers` or `actuator/loggers/com.newrelic` will result in the
+transaction name `actuator/loggers (GET)`. This is to prevent MGI.
+
+    Supported when using Spring Boot v3 and later.
+
+    This config exists in Java agent version 8.15.0+.
+  </Collapser>
+
   <Collapser
     id="ct-trace_annotation_class_name"
     title="trace_annotation_class_name"

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

@@ -94,6 +94,16 @@ Before you install the Java agent, ensure your system meets these requirements:
             v8.7.0 to current
           </td>
         </tr>
+
+        <tr>
+          <td>
+            Java 23
+          </td>
+
+          <td>
+            v8.15.0 to current
+          </td>
+        </tr>
       </tbody>
     </table>
 
@@ -152,6 +162,8 @@ The agent automatically instruments these frameworks and libraries:
     The agent automatically instruments the following frameworks. To install the Java agent on supported frameworks, see [Install the Java agent](/docs/agents/java-agent/installation/java-agent-manual-installation).
 
     * Akka 2.2.0-RC1 to latest
+    * Amazon Kinesis v1 and v2 SDKs
+    * Amazon Lambda SDK 1.11.280 to latest
     * AmazonS3 client 1.2.13 to latest
     * AmazonSNS and AmazonSNSAsync clients 1.11.12 to latest
     * AmazonSQS and AmazonSQSAsync clients 1.3.22 to latest
@@ -162,6 +174,7 @@ The agent automatically instruments these frameworks and libraries:
       * Scala 2.12: 3.2.x
       * Scala 2.13: 3.2.x
     * CXF 2.1.3 to latest
+    * Glassfish JUL (Java util logging) extension library
     * Grails 1.3.7 to 2.3.x
     * GraphQL 16.0 - latest
     * Hibernate 3.3.0.CR1 to 6.0.0.Alpha2
@@ -192,6 +205,7 @@ The agent automatically instruments these frameworks and libraries:
     * Spray 1.3.1 to latest
     * Spring 3.0.0.RELEASE to latest
     * Spring Batch 4.0.0 to latest
+    * Spring Boot Actuator v3 to latest (transaction naming)
     * Spring Web Services from 1.5.7 to latest
     * Spring Webflux 5.0.0.RELEASE to latest
     * SqsClient 2.1.0 to latest
@@ -222,6 +236,7 @@ The agent automatically instruments these frameworks and libraries:
     * Apache Httpclient from 3.1 to 5.x
     * java.net.HttpURLConnection
     * JMS from 1.1 to latest
+    * Kafka Client Node Metrics](/docs/agents/java-agent/instrumentation/java-agent-instrument-kafka-message-queues) 3.7.0 to latest (for metrics)
     * [Kafka Client Metrics](/docs/agents/java-agent/instrumentation/java-agent-instrument-kafka-message-queues) 0.10.0.0 to latest (for metrics)
     * [Kafka Client Spans](/docs/agents/java-agent/instrumentation/java-agent-instrument-kafka-message-queues) 0.11.0.0 to 3.6.x (for distributed tracing)
     * [Kafka Connect](/docs/agents/java-agent/instrumentation/java-agent-instrument-kafka-message-queues) 1.0.0 to 3.6.x (for metrics)
@@ -255,6 +270,7 @@ The agent automatically instruments these frameworks and libraries:
     * DataStax Cassandra 3.0.0 to latest (If you use [high security](/docs/accounts-partnerships/accounts/security/high-security), see the [configuration documentation for allow lists](/docs/agents/java-agent/configuration/java-agent-configuration-config-file#tt-slow_query_whitelist).)
     * DB2 9.1 to latest
     * Derby 10.11.1.1 to latest
+    * Flyway Migration Events for Flyway v8.0.0 to latest
     * Generic JDBC (any JDBC compliant driver)
     * H2 1.0.57 to latest
     * HikariCP 2.4.0 to latest

src/content/docs/apm/agents/java-agent/getting-started/compatibility-requirements-java-agent.mdx

@@ -3768,6 +3768,17 @@ For ASP.NET and .NET Framework console apps you can also configure the following
     ```
   </Collapser>
 
+  <Collapser
+    id="app-cfg-labels"
+    title="Labels"
+  >
+    ```xml
+    <appSettings>
+      <add key="NewRelic.Labels" value="key1:value1;key2:value2" />
+    </appSettings>
+    ```
+  </Collapser>
+
   <Collapser
     id="app-cfg-location"
     title="Change newrelic.config location"
@@ -3832,6 +3843,17 @@ For .NET Core apps, you can configure the following settings in `appsettings.jso
     ```
   </Collapser>
 
+  <Collapser
+    id="appsettings-json-labels"
+    title="Labels"
+  >
+    ```json
+    {
+      "NewRelic.Labels": "key1:value1;key2:value2"
+    }
+    ```
+  </Collapser>
+
   <Collapser
     id="appsettings-json-location"
     title="Change newrelic.config location"

src/content/docs/apm/agents/net-agent/configuration/net-agent-configuration.mdx

@@ -563,6 +563,26 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co
                 </td>
                 </tr>
 
+                <tr>
+                <td>
+                    Memcached
+                </td>
+
+                <td className="fcenter">
+                    <Icon
+                    style={{color: '#328787'}}
+                    name="fe-check"
+                    />
+                </td>
+
+                <td>
+                  Use [EnyimMemcachedCore](https://www.nuget.org/packages/EnyimMemcachedCore).
+
+                  * Minimum supported version: 2.0.0
+                  * Latest verified compatible version: 3.2.3
+                </td>
+                </tr>
+
             </tbody>
             </table>
 
@@ -1510,6 +1530,26 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co
                     </td>
                     </tr>
 
+                    <tr>
+                <td>
+                    Memcached
+                </td>
+
+                <td className="fcenter">
+                    <Icon
+                    style={{color: '#328787'}}
+                    name="fe-check"
+                    />
+                </td>
+
+                <td>
+                  Use [EnyimMemcachedCore](https://www.nuget.org/packages/EnyimMemcachedCore).
+
+                  * Minimum supported version: 2.0.0
+                  * Latest verified compatible version: 3.2.3
+                </td>
+                </tr>
+
                 </tbody>
                 </table>
             </Collapser>

src/content/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx

@@ -273,22 +273,22 @@ version.
 
 | Package name | Minimum supported version | Latest supported version | Introduced in* |
 | --- | --- | --- | --- |
-| `@apollo/gateway` | 2.3.0 | 2.9.1 | `@newrelic/apollo-server-plugin@1.0.0` |
+| `@apollo/gateway` | 2.3.0 | 2.9.2 | `@newrelic/apollo-server-plugin@1.0.0` |
 | `@apollo/server` | 4.0.0 | 4.11.0 | `@newrelic/apollo-server-plugin@2.1.0` |
-| `@aws-sdk/client-bedrock-runtime` | 3.474.0 | 3.654.0 | 11.13.0 |
-| `@aws-sdk/client-dynamodb` | 3.0.0 | 3.656.0 | 8.7.1 |
-| `@aws-sdk/client-sns` | 3.0.0 | 3.654.0 | 8.7.1 |
-| `@aws-sdk/client-sqs` | 3.0.0 | 3.654.0 | 8.7.1 |
-| `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.656.0 | 8.7.1 |
+| `@aws-sdk/client-bedrock-runtime` | 3.474.0 | 3.658.1 | 11.13.0 |
+| `@aws-sdk/client-dynamodb` | 3.0.0 | 3.658.1 | 8.7.1 |
+| `@aws-sdk/client-sns` | 3.0.0 | 3.658.1 | 8.7.1 |
+| `@aws-sdk/client-sqs` | 3.0.0 | 3.658.1 | 8.7.1 |
+| `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.658.1 | 8.7.1 |
 | `@aws-sdk/smithy-client` | 3.47.0 | 3.374.0 | 8.7.1 |
 | `@elastic/elasticsearch` | 7.16.0 | 8.15.0 | 11.9.0 |
 | `@grpc/grpc-js` | 1.4.0 | 1.11.3 | 8.17.0 |
 | `@hapi/hapi` | 20.1.2 | 21.3.10 | 9.0.0 |
 | `@koa/router` | 11.0.2 | 13.1.0 | 3.2.0 |
 | `@langchain/core` | 0.1.17 | 0.3.3 | 11.13.0 |
 | `@nestjs/cli` | 9.0.0 | 10.4.5 | 10.1.0 |
-| `@prisma/client` | 5.0.0 | 5.19.1 | 11.0.0 |
-| `@smithy/smithy-client` | 2.0.0 | 3.3.4 | 11.0.0 |
+| `@prisma/client` | 5.0.0 | 5.20.0 | 11.0.0 |
+| `@smithy/smithy-client` | 2.0.0 | 3.3.5 | 11.0.0 |
 | `amqplib` | 0.5.0 | 0.10.4 | 2.0.0 |
 | `apollo-server` | 3.0.0 | 3.13.0 | `@newrelic/apollo-server-plugin@1.0.0` |
 | `apollo-server-express` | 3.0.0 | 3.13.0 | `@newrelic/apollo-server-plugin@1.0.0` |
@@ -310,9 +310,9 @@ version.
 | `mysql` | 2.2.0 | 2.18.1 | 1.32.0 |
 | `mysql2` | 2.0.0 | 3.11.3 | 1.32.0 |
 | `next` | 13.4.19 | 14.2.13 | 12.0.0 |
-| `openai` | 4.0.0 | 4.63.0 | 11.13.0 |
+| `openai` | 4.0.0 | 4.65.0 | 11.13.0 |
 | `pg` | 8.2.0 | 8.13.0 | 9.0.0 |
-| `pg-native` | 2.0.0 | 3.2.0 | 9.0.0 |
+| `pg-native` | 3.0.0 | 3.2.0 | 9.0.0 |
 | `pino` | 7.0.0 | 9.4.0 | 8.11.0 |
 | `q` | 1.3.0 | 1.5.1 | 1.26.2 |
 | `redis` | 3.1.0 | 4.7.0 | 1.31.0 |