Merge branch 'develop' into NR-413646-compute-budgets

Author: adutta-newrelic

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'
 ]);
@@ -103,6 +106,10 @@ const generateReleaseNoteObject = async (filePath) => {
     description: (await excerptify(body)) ?? null,
     slug,
   };
+  
+  if (attributes.category) {
+      output.category = attributes.category;
+  }
 
   if (attributes.eolDate) {
     output.eolDate = attributes.eolDate;

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/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

@@ -276,23 +276,23 @@ supported by the agent.
 | --- | --- | --- | --- |
 | `@apollo/gateway` | 2.3.0 | 2.11.0 | `@newrelic/apollo-server-plugin@1.0.0` |
 | `@apollo/server` | 4.0.0 | 4.12.2 | `@newrelic/apollo-server-plugin@2.1.0` |
-| `@aws-sdk/client-bedrock-runtime` | 3.474.0 | 3.828.0 | 11.13.0 |
-| `@aws-sdk/client-dynamodb` | 3.0.0 | 3.828.0 | 8.7.1 |
-| `@aws-sdk/client-sns` | 3.0.0 | 3.828.0 | 8.7.1 |
-| `@aws-sdk/client-sqs` | 3.0.0 | 3.828.0 | 8.7.1 |
-| `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.828.0 | 8.7.1 |
+| `@aws-sdk/client-bedrock-runtime` | 3.474.0 | 3.830.0 | 11.13.0 |
+| `@aws-sdk/client-dynamodb` | 3.0.0 | 3.830.0 | 8.7.1 |
+| `@aws-sdk/client-sns` | 3.0.0 | 3.830.0 | 8.7.1 |
+| `@aws-sdk/client-sqs` | 3.0.0 | 3.831.0 | 8.7.1 |
+| `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.830.0 | 8.7.1 |
 | `@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.1 | 12.21.0 |
+| `@google/genai` | 1.1.0 | 1.6.0 | 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 |
-| `@langchain/core` | 0.1.17 | 0.3.58 | 11.13.0 |
+| `@langchain/core` | 0.1.17 | 0.3.61 | 11.13.0 |
 | `@nestjs/cli` | 9.0.0 | 11.0.7 | 10.1.0 |
 | `@opensearch-project/opensearch` | 2.1.0 | 3.5.1 | 12.10.0 |
-| `@prisma/client` | 5.0.0 | 6.9.0 | 11.0.0 |
-| `@smithy/smithy-client` | 2.0.0 | 4.4.3 | 11.0.0 |
+| `@prisma/client` | 5.0.0 | 6.10.1 | 11.0.0 |
+| `@smithy/smithy-client` | 2.0.0 | 4.4.4 | 11.0.0 |
 | `amqplib` | 0.5.0 | 0.10.8 | 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` |
@@ -313,10 +313,10 @@ supported by the agent.
 | `mongodb` | 4.1.4 | 6.17.0 | 1.32.0 |
 | `mysql` | 2.2.0 | 2.18.1 | 1.32.0 |
 | `mysql2` | 2.0.0 | 3.14.1 | 1.32.0 |
-| `next` | 13.4.19 | 15.3.3 | 12.0.0 |
-| `openai` | 4.0.0 | 5.3.0 | 11.13.0 |
-| `pg` | 8.2.0 | 8.16.0 | 9.0.0 |
-| `pg-native` | 3.0.0 | 3.5.0 | 9.0.0 |
+| `next` | 13.4.19 | 15.3.4 | 12.0.0 |
+| `openai` | 4.0.0 | 5.6.0 | 11.13.0 |
+| `pg` | 8.2.0 | 8.16.2 | 9.0.0 |
+| `pg-native` | 3.0.0 | 3.5.1 | 9.0.0 |
 | `pino` | 7.0.0 | 9.7.0 | 8.11.0 |
 | `q` | 1.3.0 | 1.5.1 | 1.26.2 |
 | `redis` | 3.1.0 | 5.5.6 | 1.31.0 |

src/content/docs/new-relic-control/pipeline-control/load-balancer-for-gateway.mdx

@@ -6,7 +6,7 @@ freshnessValidatedDate: never
 
 New Relic recommends implementing a load balancer for the gateway cluster.
 
-1. [Assess load requirements](/docs/pipeline-control/sizing-and-scaling):
+1. [Assess load requirements](/docs/new-relic-control/pipeline-control/sizing-and-scaling):
 
     * Determine expected data throughput and identify potential bottlenecks.
     * Evaluate the number of APM agents and peak load times.