Merge branch 'develop' into alanwest/apm-otel

Author: alanwest

package.json

@@ -18,7 +18,7 @@
     "date-fns": "^2.17.0",
     "gatsby": "4.25.7",
     "gatsby-plugin-manifest": "4.25.0",
-    "gatsby-plugin-mdx": "3.4.0",
+    "gatsby-plugin-mdx": "3.15.2",
     "gatsby-plugin-netlify": "^5.1.1",
     "gatsby-plugin-react-helmet": "^5.4.0",
     "gatsby-plugin-sharp": "4.25.1",

scripts/releaseNotes.mjs

@@ -74,6 +74,9 @@ const INCLUDE_AGENTS = new Set([
   'fluentbit',
   'nrdot',
   'prometheus',
+  'streaming_for_mobile',
+  'streaming_for_browser',
+  'streaming_for_others',
   'aws_firehose_log_forwarder',
   'aws_lambda_log_forwarder'
 ]);

src/content/docs/accounts/accounts-billing/new-relic-one-pricing-billing/compute-optimizer.mdx

@@ -0,0 +1,39 @@
+---
+title: "Optimize your compute usage"
+metaDescription: "Discover New Relic's compute optimizer to manage and reduce your compute usage. Get actionable insights and recommendations to optimize inefficient alert conditions and queries, ensuring efficient resource usage and significant savings."
+freshnessValidatedDate: never
+---
+
+The compute optimizer tool provides actionable insights to help you manage compute spend and implement automated compute controls. This means you can identify inefficient areas, receive clear recommendations for optimization, and ultimately achieve potential compute savings, improved query efficiency, and a more streamlined New Relic experience.
+
+## Access compute optimizer
+You'll find the compute optimizer in the administration panel within New Relic.
+
+1. Log in to New Relic.
+2. Open your personal settings by clicking your user name in the bottom-left corner of the New Relic interface. Go to the administration panel.
+3. Click **compute optimizer** to access the dashboard.
+
+<img
+  title="Compute optimizer dashboard"
+  alt="Image of the compute optimizer dashboard"
+  src="/images/compute_optimizer.webp"
+/>
+
+## The compute optimizer dashboard
+The compute optimizer dashboard presents two crucial metrics:
+
+- **Inefficient usage:** This provides an overview several of inefficient compute areas identified in your account.
+- **Potential savings:** This metric quantifies the estimated savings you can achieve by implementing the recommendations provided by the tool.
+
+### Recommendations
+The core of the compute optimizer is the recommendations table, which breaks down the identified optimization opportunities:
+
+- **Component name:** Identifies the specific item or instance that has an optimization opportunity (for example, the name of a particular alert condition). 
+- **Product capability:**  Identifies the broader New Relic product capability associated with the optimization opportunity. The initial release focuses on alert conditions.
+- **CCU usage:** Provides an understanding of the current compute consumption (CCU usage) for each listed component, helping you understand its current impact.
+- **Recommendation:** Offers actionable insights for optimizing your compute. For example, you might see a recommendation to "Add a `WHERE` clause outside the `SELECT` statement," which could save a significant percentage of CCUs for a specific alert condition.
+- **CCU savings estimate:** This quantifies the potential compute reduction for each individual recommendation listed in the table. For example, if a recommendation is to optimize **alert X**, this column shows the specific CCU savings you could achieve just for **alert X**. All these individual CCU savings estimate values suggested in each row are then added together to calculate the total potential savings metric.
+
+All insights presented in the compute optimizer are dynamic and based on your time picker settings, allowing you to analyze data relevant to specific periods.
+
+The action menu for each recommendation offers an optimized query wherever applicable, making it easy to implement the suggested changes directly.

src/content/docs/agentic-ai/knowledge-integration/overview.mdx

@@ -27,9 +27,9 @@ This RAG approach significantly improves the accuracy and relevance of the respo
 
 ## Key features
 With New Relic AI knowledge connector, you can:
-- **Resolve incidents faster:** Gain immediate access to relevant context from your internal runbooks and documentation directly within New Relic AI, leading to quicker mean time to resolution (MTTR).
-- **Get actionable, tailored recommendations:** The answers provided are specific to your environment and based on your own best practices and historical data.
-- **Answer critical, context-specific questions:** Easily find solutions to problems that have been solved before. Ask questions like:
+- Gain access to relevant context from your internal runbooks and documentation directly within New Relic AI, leading to quicker mean time to resolution (MTTR).
+- The answers provided are specific to your environment and based on your own best practices and historical data.
+- Easily find solutions to problems that have been solved before. Ask questions like:
   - "Who has resolved similar issues in the past?"
   - "What are the standard triage steps for this type of alert?"
   - "Show me the runbook for a `database connection limit exceeded` error."
@@ -54,17 +54,17 @@ This flexibility allows your organization to control who has the ability to mana
 ## Configure data source and indexing frequency [#configure]
 You can connect your knowledge sources using either pre-built connectors or the [knowledge connector API](/docs/apis/nerdgraph/examples/nerdgraph-rag) for more custom integrations.
 
-To start indexing your Confluence content, you need:
+To start indexing Confluence content, you need:
 
 - Confluence URL with your unique Confluence cloud ID: https://api.atlassian.com/ex/confluence/[cloud_id]
 - A Confluence API key with the following minimum required scopes:
   - `read:confluence-content.all`
   - `read:confluence-space.summary`
   - `read:content:confluence`
   - `read:content-details:confluence`
+- Relevant query parameter using Confluence Query Language (CQL) to filter the list of returned content to be indexed
 
-
-To start indexing your Confluence content and benefit from the knowledge connector with New Relic AI, follow the mentioned steps:
+To start indexing your content and benefit from the knowledge connector with New Relic AI, follow the mentioned steps:
 
 <Steps>
 
@@ -77,7 +77,7 @@ To start indexing your Confluence content and benefit from the knowledge connect
   </Step>
 
   <Step>
-      Select <DNT>**Confluence NRAI Knowledge Connector**</DNT>.
+      Select <DNT>**one of the available connectors**</DNT>.
   </Step>
 
   <Step>
@@ -103,7 +103,7 @@ To start indexing your Confluence content and benefit from the knowledge connect
             </td>
 
             <td>
-              Enter a unique name for your connector, example <DNT>**Demo connector**</DNT>.
+              Enter a unique name for your connector (example, <DNT>Demo Connector</DNT>).
             </td> 
           </tr>
 
@@ -196,7 +196,7 @@ To start indexing your Confluence content and benefit from the knowledge connect
 ## Data synchronization and querying [#data-sync-query]
 Once your data source is connected, New Relic will begin to synchronize and index your knowledge articles. After the initial synchronization is complete, your team can begin asking questions through the New Relic AI chat. Additionally, New Relic AI will automatically use the knowledge connector tool to search your indexed documents and provide contextual responses on the “What happened previously?” portion of the [issue page](/docs/alerts/incident-management/Issues-and-Incident-management-and-response/#issue-summary). 
 
-## Supported connectors:
+## Supported connectors
 
 <Callout title="important">
   If you’d like to make a request for an unsupported connector, fill out this [form](https://forms.gle/ZHs4mpFKdsqtfNJW7).

src/content/docs/alerts/admin/rules-limits-alerts.mdx

@@ -325,6 +325,26 @@ This page describes limits and rules pertaining to New Relic <InlinePopover type
         [Depends on channel](/docs/alerts/get-notified/intro-notifications/#channels)
       </td>
     </tr>
+
+    <tr>
+      <td id="destination">
+          Destination
+      </td>
+      <td>
+        Destination limitations
+      </td>
+      <td>
+        1 Destination
+      </td>
+      <td>
+        * EMAIL: 10k
+        * WEBHOOK: 10k
+        * Slack: 10k
+        * PAGERDUTY_SERVICE_INTEGRATION: 20k
+        * Other than that: 5k
+      </td>
+    </tr>
+
   </tbody>
 </table>
 

src/content/docs/apis/nerdgraph/get-started/introduction-new-relic-nerdgraph.mdx

@@ -100,13 +100,14 @@ Here are all our available NerdGraph docs:
   <tbody>
     <tr>
       <td>
-        Account management
+        Account and user management
       </td>
 
       <td>
         * [Manage accounts](/docs/apis/nerdgraph/examples/manage-accounts-nerdgraph)
         * [Manage users](/docs/apis/nerdgraph/examples/nerdgraph-manage-users)
-        * [Manage user groups](/docs/apis/nerdgraph/examples/nerdgraph-user-mgmt)
+        * [Manage user groups](/docs/apis/nerdgraph/examples/nerdgraph-manage-groups)
+        * [Manage roles](/docs/apis/nerdgraph/examples/nerdgraph-manage-groups/#create-role)
         * [Create and manage API keys](/docs/apis/nerdgraph/examples/use-nerdgraph-manage-license-keys-user-keys) (data ingest keys, and user keys)
       </td>
     </tr>
@@ -396,4 +397,4 @@ The following are terms that originate with GraphQL, the API format NerdGraph us
       </td>
     </tr>
   </tbody>
-</table>
+</table>

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

@@ -284,7 +284,7 @@ supported by the agent.
 | `@aws-sdk/smithy-client` | 3.47.0 | 3.374.0 | 8.7.1 |
 | `@azure/functions` | 4.7.0 | 4.7.3-beta.0 | 12.18.0 |
 | `@elastic/elasticsearch` | 7.16.0 | 9.0.2 | 11.9.0 |
-| `@google/genai` | 1.1.0 | 1.5.0 | 12.21.0 |
+| `@google/genai` | 1.1.0 | 1.5.1 | 12.21.0 |
 | `@grpc/grpc-js` | 1.4.0 | 1.13.4 | 8.17.0 |
 | `@hapi/hapi` | 20.1.2 | 21.4.0 | 9.0.0 |
 | `@koa/router` | 11.0.2 | 13.1.0 | 3.2.0 |
@@ -338,11 +338,9 @@ Through the `@aws-sdk/client-bedrock-runtime` module, we support:
 
 | Model | Image | Text | Vision |
 | --- | --- | --- | --- |
-| AI21 Labs Jurassic-2 | ❌ | ✅ | - |
 | Amazon Titan | ❌ | ✅ | - |
 | Anthropic Claude | ❌ | ✅ | ❌ |
 | Cohere | ❌ | ✅ | - |
-| Meta Llama2 | ❌ | ✅ | - |
 | Meta Llama3 | ❌ | ✅ | - |
 
 Note: if a model supports streaming, we also instrument the streaming variant.

src/content/docs/browser/browser-monitoring/browser-pro-features/session-replay/get-started.mdx

@@ -17,7 +17,7 @@ Session replay captures interactions on your web app and maps other telemetry da
 <img
   title="Session replay details"
   alt="Screenshot of session replay details"
-  src="/images/browser_screenshot-full_session-replay-details.gif"
+  src="/images/session_replay_player.webp"
 />
 
 ## How session replay works [#how-it-works]

src/content/docs/browser/new-relic-browser/browser-pro-features/marks-and-measures.mdx

@@ -32,15 +32,15 @@ To enable this feature:
 
 Once enabled, the agent stores marks and measures data under the `BrowserPerformance` event type in New Relic. To find this data, try the following queries and then create custom dashboards to track performance.
 
-**Query 1**: This NRQL query retrieves all `BrowserPerformance` events for the specified `appName` ("My Application") where the `entryName` is either `mark` or `measure`. 
+**Query 1**: This NRQL query retrieves all `BrowserPerformance` events for the specified `appName` ("My Application") where the `entryType` is either `mark` or `measure`. 
 
     ```nrql
-    FROM BrowserPerformance SELECT * WHERE appName = 'My Application' AND entryName = 'mark' OR entryName = 'measure'
+    FROM BrowserPerformance SELECT * WHERE appName = 'My Application' AND entryType = 'mark' OR entryType = 'measure'
     ```
 
-**Query 2**: This NRQL query calculates the average `entryDuration` for mark and measure events within the specified `appName`. The `FACET entryName` clause groups the results by the `entryName` field, providing separate average durations for mark and measure events. This can be useful for comparing the average performance of marks versus measures. 
+**Query 2**: This NRQL query calculates the average `entryDuration` for measure events within the specified `appName`. The `FACET entryName` clause groups the results by the `entryName` field, providing separate average durations for unique measure events. This can be useful for comparing the average performance of individual measures. 
 
     ```nrql
-    FROM BrowserPerformance SELECT average(entryDuration) WHERE appName = 'My Application' AND entryName = 'mark' OR entryName = 'measure' FACET entryName
+    FROM BrowserPerformance SELECT average(entryDuration) WHERE appName = 'My Application' AND entryType = 'measure' FACET entryName
     ```
 

src/content/docs/browser/new-relic-browser/troubleshooting/how-to-debug-browser-agent.mdx

@@ -0,0 +1,80 @@
+---
+title: How to debug the New Relic Browser Agent
+type: troubleshooting
+tags:
+  - Browser
+  - Browser monitoring
+  - Troubleshooting
+metaDescription: Learn how to debug the New Relic Browser Agent live in your browser.
+freshnessValidatedDate: never
+---
+
+## Problem
+
+You need to debug an issue with the New Relic Browser Agent and want to to better understand live agent behaviors and data collection.
+
+## Solution
+
+If your application is instrumented with [<InlinePopover type="browser"/>](/docs/browser/new-relic-browser/installation-configuration/troubleshooting-browser-monitoring-installation) and you want to inspect agent activity, follow these steps:
+
+<Steps>
+
+  <Step>
+
+    ## Enable debug logging [#enable-debug-logging]
+
+    To get more insight into the agent's activity, [enable debug logging](/docs/browser/browser-monitoring/browser-pro-features/browser-logs/get-started/).
+
+    The browser agent emits warning codes using `console.debug`, and this setting will capture those logs to your New Relic browser application, helping you track agent activity and problems.
+
+    ## Inspect agent logs [#inspect-agent-logs]
+
+    To inspect locally, open your browser's developer console and look for `debug` messages prefixed with `New Relic Warning:`. These messages indicate agent issues, tied to known [warning codes](https://github.com/newrelic/newrelic-browser-agent/blob/main/docs/warning-codes.md).
+
+    To inspect agent logs across all instances of your web application, [check your logs](/docs/browser/browser-monitoring/browser-pro-features/browser-logs/view-browser-logs/logs-of-a-browser-app/) on [one.newrelic.com](https://one.newrelic.com).
+
+    These logs can help you identify known issues with the browser agent and its configuration within your pages.
+
+  </Step>
+
+  <Step>
+
+    ## Monitor network requests [#monitor-network-requests]
+
+    Use the Network tab in your browser's developer tools to monitor requests sent by the agent. Look for calls to domains like `bam.nr-data.net` or `js-agent.newrelic.com`.
+
+    If you see failed requests or errors, check for network issues, ad blockers, or CSP rules that might be interfering with agent communication.
+
+    Expected endpoints under `js-agent.newrelic.com`:
+    - PageView: `/`
+    - AjaxRequest, BrowserInteraction, PageViewTiming: `/events`
+    - PageAction, BrowserPerformance, UserAction, Custom Events: `/ins`
+    - Log: `/browser/logs`
+    - JavaScriptError, Ajax Timeslice Metrics: `/jserrors/`
+    - SessionReplay, SessionTrace: `browser/blobs`
+
+  </Step>
+
+  <Step>
+
+    ## Use inspection events for troubleshooting [#use-inspection-events]
+
+    The agent emits inspection events that can be captured for deeper troubleshooting. To listen for these events, you can add a listener in your console:
+
+    ```js
+    document.addEventListener('newrelic', function(e) {
+      console.log('NR Inspection Event:', e.detail);
+    });
+    ```
+
+    This will log inspection events emitted by the agent, providing details about feature status, errors, lifecycles, harvesting and configuration.
+
+    **Note:** Inspection events are available in agent versions 1.285.0 and higher. Inspection events are emitted immediately upon creation in the agent, any events emitted by the agent before the above event listener is created on the end-user machine will be missed.
+
+  </Step>
+
+</Steps>
+
+<Callout variant="tip">
+If you need further assistance with debugging or interpreting inspection events, or debugging problems with your web application and New Relic, visit [support.newrelic.com](https://support.newrelic.com) for help.
+</Callout>

src/content/docs/infrastructure/microsoft-azure-integrations/get-started/azure-native.mdx

@@ -17,7 +17,8 @@ The Azure Native New Relic Service lets you:
 On top of that, you can then use New Relic for other non-Azure-related monitoring you might need, using any of [our 500+ integrations](https://newrelic.com/instant-observability).
 
 <Callout variant="important">
-  This service is only available for customers who opt to have Azure host their New Relic data.
+  * This service is only available for customers who opt to have Azure host their New Relic data. 
+  * To avoid incurring additional charges ensure that the diagnostic settings on Azure resources are set accordingly or disable forwarding via Azure Native New Relic Service to avoid data being forwarded to New Relic platform. 
 </Callout>
 
 ## Notes on available New Relic features [#features]

src/content/docs/new-relic-control/pipeline-control/data-dropping-gateway.mdx

@@ -44,7 +44,7 @@ Some attributes are only added during the enrichment process (after gateway, bef
 - **Cannot** be used in NRQL queries for gateway drop rules (since they don't exist at that point)
 
 ### Best practices
-When [authoring gateway rules](/docs/new-relic-control/pipeline-control/create-pipeline-rules.mdx), be aware that some attributes may not be available at the gateway level. If you need to use attributes that are only added during enrichment, consider using a cloud rule instead of a gateway rule.
+When [authoring gateway rules](/docs/new-relic-control/pipeline-control/create-pipeline-rules), be aware that some attributes may not be available at the gateway level. If you need to use attributes that are only added during enrichment, consider using a cloud rule instead of a gateway rule.
 
 ## Data types and attribute handling
 The following table lists:
@@ -167,4 +167,4 @@ The following table lists:
             <td>`DELETE FROM ContainerSample WHERE agentName='ContainerSampleAgent'`</td>
         </tr>
     </tbody>
-</table>
+</table>