Daily merge 11 13 25/night

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.12.4",
+    "@newrelic/gatsby-theme-newrelic": "9.14.0",
     "@splitsoftware/splitio-react": "^1.2.4",
     "ansi-colors": "^4.1.3",
     "cockatiel": "^3.0.0-beta.0",

src/content/docs/alerts/incident-management/response-intelligence-ai.mdx

@@ -30,7 +30,15 @@ The AI-powered issue page provides a concise summary that includes the affected
   src="/images/nr-ai-summary.webp"
 />
 
-**What’s impacted?**<br/>
+## Access AI summary [#access-ai-summary]
+
+To view the AI summary for any alert issue:
+
+1. Go to **[one.newrelic.com](https://one.newrelic.com) > Alerts > Issues & activity**.
+2. Select an alert issue.
+3. Expand the <DNT>**AI summary**</DNT> section.
+
+**What's impacted?**<br/>
 First responders need to assess the "blast radius" to determine the severity of an issue and decide on the next steps. This widget provides an overview of the affected entities along with the impact to the end users of the application or service.
 
 **What happened previously?**<br/>
@@ -39,7 +47,7 @@ Many IT issues tend to reoccur. Knowing if an issue has happened before, why it
 **What to check?**<br/>
 First responders often need contextual guidance on immediate actions to mitigate an issue. This widget provides customized steps to help them quickly restore services to normal operational levels. Additionally, the Potential causes tab identifies likely causes through causal analysis, covering a range of possible anomalies and performance issues. For more information, refer to casual analysis.
 
-## Causal analysis
+## Causal analysis [#causal-analysis]
 The causal analysis engine identifies potential symptoms that might have triggered an alert event and suggests immediate mitigating actions to address them.
 
 Consider a scenario where a PHP application encounters a memory leak, leading to a failure in the throughput SLI and triggering an alert. Our engine investigates by moving from the service level to the APM application and then to the infrastructure container to detect the symptom.
@@ -55,11 +63,36 @@ At the moment, New Relic only supports causal analysis for APM entities.
   src="/images/potential_issues.webp"
 />
 
-### Mitigating actions & visualizations
+### Mitigating actions & visualizations [#mitigating-actions-visualizations]
 
 For every identified potential cause, the engine offers tailored mitigation actions that guide users through the necessary steps to quickly restore services and entities to their normal operational states. We recognize that many of our customers typically rely on NRQL to analyze significant queries, hence we provide relevant visuals alongside the underlying query for each cause.
 
-### New Relic AI generated analysis
+### New Relic AI generated analysis [#ai-generated-analysis]
 
 In some scenarios, our causal engine may not identify an algorithm-driven cause. However, we have insights that, when combined with with LLMs, can offer you actionable steps. To access this capability, you must have the New Relic AI entitlement enabled.
 
+## AI log summarization for log-based alerts [#ai-log-summarization]
+
+For alert issues triggered by log conditions, the AI summary provides enhanced analysis by automatically examining up to 100,000 log entries from a contextual time window around your alert. This log analysis surfaces patterns, anomalies, and potential causes that aren't immediately visible in the alert itself.
+
+When you expand the <DNT>**AI summary**</DNT> section for a log-based alert, following are details you'll get:
+
+* <DNT>**Analysis context**</DNT>: The number of logs analyzed, time range, and entity name.
+* <DNT>**What happened**</DNT>: A summary explaining the incident with insights beyond the alert itself.
+* <DNT>**Findings (3-4)**</DNT>: Key patterns and anomalies with a specific remediation step.
+
+<img
+  title="The alerts issues feed."
+  alt="A screenshot of the alerts issues
+  feed."
+  src="/images/ai-log-summary.webp"
+/>
+
+To explore findings in detail, click into each finding. This displays comprehensive information below the AI summary section, including:
+
+* Detailed explanation of each finding.
+* Specific remediation steps to resolve the issue.
+
+This log-specific analysis helps you understand potential causes and resolve incidents faster by automatically surfacing critical information from thousands of log entries.
+
+

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

@@ -114,6 +114,16 @@ Before you install the Java agent, ensure your system meets these requirements:
             v8.20.0 to current
           </td>
         </tr>
+
+        <tr>
+          <td>
+            Java 25
+          </td>
+
+          <td>
+            v8.25.0 to current
+          </td>
+        </tr>
       </tbody>
     </table>
 
@@ -199,6 +209,7 @@ The agent automatically instruments these frameworks and libraries:
     * Jersey 1.0.1 to latest
     * JSF (Java Server Faces)
     * JUL (Java util logging) (for our [logs in context](/docs/logs/logs-context/java-configure-logs-context-all/) feature)
+    * Kotlin Coroutines 1.4.0 to latest
     * Log4j1 1.2.17 to latest (for our [logs in context](/docs/logs/logs-context/java-configure-logs-context-all/) feature)
     * Log4j2 2.6 to latest (for our [logs in context](/docs/logs/logs-context/java-configure-logs-context-all/) feature)
     * Logback 1.1 to latest (for our [logs in context](/docs/logs/logs-context/java-configure-logs-context-all/) feature)

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

@@ -126,6 +126,14 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co
                     10.0.0 and higher
                 </td>
                 </tr>
+                <tr>
+                <td>
+                    .NET 10.0
+                </td>
+                <td>
+                    10.0.0 and higher
+                </td>
+                </tr>
             </tbody>
             </table>
 

src/content/docs/apm/agents/php-agent/advanced-installation/install-new-relic-php-agent-gae-flexible-environment.mdx

@@ -50,6 +50,12 @@ For more information about deploying and configuring your PHP app in the GAE fle
     RUN DEBIAN_FRONTEND=noninteractive apt-get update && DEBIAN_FRONTEND=noninteractive apt-get -y install newrelic-php5
     RUN NR_INSTALL_KEY="new-relic-license-key" NR_INSTALL_SILENT=true newrelic-install install
     ```
+
+    NOTE: For Debian Trixie and later use the following `wget` command instead:
+
+    ```dockerfile
+    wget -O- https://download.newrelic.com/NEWRELIC_APT_2DAD550E.public | sudo gpg --dearmor -o /usr/share/keyrings/download.newrelic.com-newrelic.gpg
+    ```
   </Collapser>
 
   <Collapser

src/content/docs/apm/agents/php-agent/installation/php-agent-installation-ubuntu-debian.mdx

@@ -34,10 +34,18 @@ This is the recommended method for New Relic installation and maintenance.
 
     #### 1. Trust the New Relic GPG key
 
+       For all Ubuntu releases and Debian releases _before_ Debian Trixie use:
+
        ```bash
        wget -O- https://download.newrelic.com/NEWRELIC_APT_2DAD550E.public | sudo gpg --import --batch --no-default-keyring --keyring /usr/share/keyrings/download.newrelic.com-newrelic.gpg
        ```
 
+       For Debian Trixie and later use:
+
+       ```bash
+       wget -O- https://download.newrelic.com/NEWRELIC_APT_2DAD550E.public | sudo gpg --dearmor -o /usr/share/keyrings/download.newrelic.com-newrelic.gpg
+       ```
+
        This command installs New Relic's GPG key used by `apt` to verify signatures of packages in `http://apt.newrelic.com/debian/` apt repository added in next step.
 
     #### 2. Add `http://apt.newrelic.com/debian/` apt repository to `sources.list`

src/content/docs/apm/agents/python-agent/getting-started/instrumented-python-packages.mdx

@@ -172,7 +172,7 @@ To request built-in instrumentation for additional packages, get support at [sup
 
   <Collapser
     id="flask"
-    title={<ExternalLink href="http://flask.pocoo.org/">Flask</ExternalLink>}
+    title={<ExternalLink href="https://flask.palletsprojects.com">Flask</ExternalLink>}
   >
     Function timing in transactions traces for slow transactions is provided for:
 

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

@@ -3138,6 +3138,18 @@ When middleware instrumentation is disabled, if an application is using middlewa
   An array of strings that will collectively serve as a denylist for filtering which Sidekiq job arguments get reported to New Relic. To capture any Sidekiq arguments, 'job.sidekiq.args.*' must be added to the separate `:'attributes.include'` configuration option. Each string in this array will be turned into a regular expression via `Regexp.new` to permit advanced matching. For job argument hashes, if either a key or value matches the pair will be excluded. All matching job argument array elements and job argument scalars will be excluded.
   </Collapser>
 
+  <Collapser id="sidekiq-ignore_retry_errors" title="sidekiq.ignore_retry_errors">
+    <table>
+      <tbody>
+        <tr><th>Type</th><td>Boolean</td></tr>
+        <tr><th>Default</th><td>`false`</td></tr>
+        <tr><th>Environ variable</th><td>`NEW_RELIC_SIDEKIQ_IGNORE_RETRY_ERRORS`</td></tr>
+      </tbody>
+    </table>
+
+  If `true`, the agent will ignore exceptions raised during Sidekiq's retry attempts and will only report the error if the job permanently fails.
+  </Collapser>
+
 </CollapserGroup>
 
 ## Slow SQL [#slow-sql]

src/content/docs/browser/new-relic-browser/getting-started/compatibility-requirements-browser-monitoring.mdx

@@ -124,10 +124,6 @@ Instrumentation and specific features may be compatible with other browsers or v
   </tbody>
 </table>
 
-<Callout variant="important">
-  When you use browser monitoring with cookies, New Relic's cookies are a third-party cookie on your site, and may not store or work on certain web browsers used by your visitors. See the applicable browser's websites for details about their compatibility with third-party cookies.
-</Callout>
-
 ## APM agents [#apm-agents]
 
 One way to [deploy browser monitoring](/docs/browser/new-relic-browser/getting-started/adding-apps-new-relic-browser) for an app is using one of our APM agents.

src/content/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8250.mdx

@@ -0,0 +1,96 @@
+---
+subject: Java agent
+releaseDate: '2025-11-12'
+version: 8.25.0
+downloadLink: 'https://download.newrelic.com/newrelic/java-agent/newrelic-agent/8.25.0/'
+features: [“Adds Java 25 Support”, “Adds Logback-1.5.20 Support”, “Introduces a config option to update Spring Controller transaction naming”]
+bugs: [“Error Class Naming: fixed parsing logic”, “Error Logging: fixed potential memory issue”]
+security: []
+---
+<ButtonGroup>
+  <ButtonLink
+    role="button"
+    to="https://download.newrelic.com/newrelic/java-agent/newrelic-agent/8.25.0/"
+    variant="primary"
+  >
+    Download this agent version
+  </ButtonLink>
+</ButtonGroup>
+
+## New features and improvements
+
+- Adds Java 25 Support by @deleonenriqueta in [2512](https://github.com/newrelic/newrelic-java-agent/pull/2512)
+- Adds support for Logback-1.5.20 by @jtduffy in [2535](https://github.com/newrelic/newrelic-java-agent/pull/2535)
+- Introduces a config option to disable the execution of the `call` and `exec` SQL parser regular expressions by @jtduffy in [2490](https://github.com/newrelic/newrelic-java-agent/pull/2490)
+- Adds support for Kotlin Coroutines v1.4+ by @dhilpipre in [2454](https://github.com/newrelic/newrelic-java-agent/pull/2454)
+- Adds support for Kotlin Coroutines Suspend Functions generated outside of Kotlin Coroutines by @dhilpipre in [2456](https://github.com/newrelic/newrelic-java-agent/pull/2456)
+- Introduces a preference config for multiple hosts during datastore detection by @jbedell-newrelic in [2508](https://github.com/newrelic/newrelic-java-agent/pull/2508)
+- Adds a system property to configure the artifact skip function by @jtduffy in [2509](https://github.com/newrelic/newrelic-java-agent/pull/2509)
+- Adds a configuration option allowing Spring Controller transactions to be named using the controller class name and method name by @sharvath-newrelic in [2532](https://github.com/newrelic/newrelic-java-agent/pull/2532)
+- Implements SamplerConfig, centralizing all `distributed_tracing.sampler` configs into the `SamplerConfig` by @jasonjkeller in [2529](https://github.com/newrelic/newrelic-java-agent/pull/2529)
+- Updates `kafka-clients-spans-0.11.0.0` producer instrumentation to use modern distributed tracing API’s with W3C Trace Context support by @sharvath-newrelic in [2516](https://github.com/newrelic/newrelic-java-agent/pull/2516)
+
+## Fixes
+
+- Fixes parsing of error class names by @sharvath-newrelic in [2497](https://github.com/newrelic/newrelic-java-agent/pull/2497)
+- Fixes a potential memory issue caused by excessively large stack traces in error logging by @jtduffy in [2498](https://github.com/newrelic/newrelic-java-agent/pull/2498)
+- Clarify logging messages for invalid attributes on custom events and logging events by @sharvath-newrelic in [2501](https://github.com/newrelic/newrelic-java-agent/pull/2501)
+
+## Deprecations
+
+- `aws-wrap-0.7.0`
+- `java.completable-future-jdk8`
+- `play-2.3`
+- `netty-3.4`
+- `Struts v1`
+
+## Update to latest version [#procedures]
+
+To identify which version of the Java agent you're currently using, run `java -jar newrelic.jar -v`. Your Java agent version will be printed to your console.
+
+Then, to update to the latest Java agent version:
+
+1. Back up the **entire** [Java agent root directory](/docs/agents/manage-apm-agents/troubleshooting/find-agent-root-directory#java-agent) to another location. Rename that directory to `NewRelic_Agent#.#.#`, where `#.#.#` is the agent version number.
+2. [Download the agent.](/docs/release-notes/agent-release-notes/java-release-notes).
+3. Unzip the new agent download file, then copy `newrelic-api.jar` and `newrelic.jar` into the original [Java agent root directory](/docs/agents/manage-apm-agents/troubleshooting/find-agent-root-directory#java-agent).
+4. Compare your old `newrelic.yml` with the newly downloaded `newrelic.yml` from the zip, and [update the file if needed](#diff).
+5. Restart your Java dispatcher.
+
+If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.
+
+## Update agent config differences [#diff]
+
+We add new settings to `newrelic.yml` as we release new versions of the agent. You can use `diff` or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings.
+
+For example, if you `diff` the default `newrelic.yml` files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:
+
+```yaml
+➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
+...
+107a108,119
+>       # Whether the log events should include context from loggers with support for that.
+>       include_context_data:
+>
+>         # When true, application logs will contain context data.
+>         enabled: false
+>
+>         # 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 not be sent to New Relic.
+>         #exclude:
+>
+125a138
+>
+128c141
+<     enabled: false
+---
+>     enabled: true
+...
+```
+
+In this example, these lines were added to the default `newrelic.yml` in Java agent version 7.11.0. If you're moving to 7.11.0 or higher, you should add these new lines to your original `newrelic.yml`.
+
+## Support statement:
+
+* New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach [end-of-life](https://docs.newrelic.com/docs/using-new-relic/cross-product-functions/install-configure/notification-changes-new-relic-saas-features-distributed-software/).

src/content/docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-23-0.mdx

@@ -0,0 +1,31 @@
+---
+subject: Ruby agent
+releaseDate: '2025-11-12'
+version: 9.23.0
+downloadLink: https://rubygems.org/downloads/newrelic_rpm-9.23.0.gem
+features: ["Add sidekiq.ignore_retry_errors configuration option", "Deprecation notice for recording deployments using Capistrano", "Use remote parent sampling configurations for decisions in more scenarios"]
+bugs: []
+security: []
+---
+
+<Callout variant="important">
+  We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about [keeping agents up to date](/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/).
+
+  See the New Relic Ruby agent [EOL policy](/docs/apm/agents/ruby-agent/getting-started/ruby-agent-eol-policy/) for information about agent releases and support dates.
+</Callout>
+
+## v9.23.0
+
+- **Feature: Add sidekiq.ignore_retry_errors configuration option**
+
+  A new configuration option, `sidekiq.ignore_retry_errors`, has been added to control if Sidekiq job retries are captured. Retry errors are captured by default, but now if `sidekiq.ignore_retry_errors` is set to `true`, the agent will ignore exceptions raised during Sidekiq's retry attempts and will only report the error if the job permanently fails. Thank you [DonGiulio](https://github.com/DonGiulio) for recognizing this improvement and contributing a solution. [PR#3317](https://github.com/newrelic/newrelic-ruby-agent/pull/3317)
+
+- **Feature: Deprecation notice for recording deployments using Capistrano**
+
+  Sending application deployment information using a Capistrano recipe is deprecated and will be removed in agent version 10.0.0. For recording deployments, please see our guide to [Change Tracking](https://docs.newrelic.com/docs/change-tracking/change-tracking-introduction/) for a list of available options.
+
+- **Feature: Use remote parent sampling configurations for decisions in more scenarios**
+
+  Previously, the `distributed_tracing.sampler.remote_parent_sampled` and `distributed_tracing.sampler.remote_parent_not_sampled` configuration options were used for the sampling decision only when the `traceparent` and `tracestate` headers were present. Now, these configuration options are applied in cases when the `tracestate` header is missing and when only the `newrelic` header is available. This change makes distributed trace sampling more consistent and predictable. [PR#3306](https://github.com/newrelic/newrelic-ruby-agent/pull/3306)
+
+

src/content/eol/2025/11/eol-chrome-140-node-22-synthetics.md

@@ -22,11 +22,7 @@ The following upgrades will be implemented:
 The following monitor types will be affected by these changes:
 
 * Scripted Browser
-* Step Monitor
-* Simple Browser Monitors
 * Scripted API
-* Cert Check
-* Broken Link
 
 **Note:** Moving to Chrome 140 automatically upgrades to Node.js 22.
 
@@ -55,24 +51,11 @@ In the creation/edit monitor screen, you'll see the ability to select Chrome bro
 * Chrome 134
 * Chrome 140
 
-<img
-  title="Chrome version"
-  alt="Image of the Chrome version changes"
-  src="/images/runtime-synthetic.webp"
-/>
-
 
 ### For other monitor types
 
 Select the runtime in the Configure monitor screen.
 
-<img
-  title="node runtime"
-  alt="Image of the node runtime changes"
-  src="/images/node-synthetic-runtime.webp"
-/>
-
-
 
 
 ## What you need to do during the transition period

src/layouts/HomePageLayout.js

@@ -83,7 +83,7 @@ const HomePageLayout = ({ children, pageContext }) => {
             <Layout.Footer
               fileRelativePath={pageContext.fileRelativePath}
               css={css`
-                height: 60px;
+                height: 70px;
               `}
             />
           </Layout>