Merge branch 'develop' into RAG-documentation-update

Author: tejaswaroop-nr

gatsby-config.js

@@ -432,19 +432,13 @@ module.exports = {
           ],
         },
         newrelic: {
-          config: {
+          config: process.env.ENVIRONMENT === 'production' && {
             instrumentationType: 'proAndSPA',
             accountId: '10956800',
             trustKey: '1',
-            agentID:
-              process.env.ENVIRONMENT === 'production'
-                ? '35094662'
-                : '35094418',
+            agentID: '35094662',
             licenseKey: 'NRJS-649173eb1a7b28cd6ab',
-            applicationID:
-              process.env.ENVIRONMENT === 'production'
-                ? '35094662'
-                : '35094418',
+            applicationID: '35094662',
             beacon: 'staging-bam-cell.nr-data.net',
             errorBeacon: 'staging-bam-cell.nr-data.net',
             settings: {

src/content/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing.mdx

@@ -20,4 +20,4 @@ In addition to the primary billing factors of GB Ingested and billable users, yo
 * **Extended Retention for Original Data or Data Plus**: This add-on applies if you exceed the default length of time your data is retained. This applies to all your data—not just logs—and is a good option if you need to make a lot of small queries or make queries on large volumes of data.
 * **Live Archives**: Extend your log storage duration up to seven years. Live Archives also requires Advanced Compute.
 * **New Relic Synthetic Checks**: This add-on applies if your Checks exceed the default number of synthetic monitor checks.
-* **Vulnerability Management**: This feature is included with Data Plus, but the add-on applies if you use the Vulnerability Management feature without Data Plus.
+* **Security RX**: This feature is included with Data Plus, but the add-on applies if you use the Security RX feature without Data Plus.

src/content/docs/accounts/accounts-billing/new-relic-one-pricing-billing/compute-budgets/account-level.mdx

@@ -1,5 +1,15 @@
 ---
 title: Account level budgets
+tags:
+  - Compute Budgets
+  - Account level compute budgets
+  - Account budgets
+  - Compute usage
+  - Budgets
+  - CCU usage
+  - CCU budget
+  - CCU limits
+  - What is account level budget
 metaDescription: Set up custom budgets in New Relic to proactively manage your Compute Consumption Unit (CCU) usage and costs.
 freshnessValidatedDate: never
 ---

src/content/docs/accounts/accounts-billing/new-relic-one-pricing-billing/compute-budgets/organization-level-budgets.mdx

@@ -1,5 +1,15 @@
 ---
 title: Organization level budgets
+tags:
+  - Compute Budgets
+  - Organization level compute budgets
+  - Organization budgets
+  - Compute usage
+  - Budgets
+  - CCU usage
+  - CCU budget
+  - CCU limits
+  - What is Organization level budget
 metaDescription: Manage your organization's Compute Budgets to monitor and alert on Compute Consumption Unit (CCU) usage.
 freshnessValidatedDate: never
 ---

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

@@ -1,9 +1,13 @@
 ---
 title: Getting started with Compute Budgets
 tags:
-  - Overview about compute budgets
-  - compute budgets
-  - what is compute budgets
+  - Overview about Compute Budgets
+  - Compute Budgets
+  - What is Compute Budgets
+  - Compute Budgets overview
+  - Budgets
+  - CCU usage
+  - Gettings started with Compute Budgets
 metaDescription: Monitor and control your Compute Consumption Unit (CCU) usage with New Relic's Compute Budgets feature.
 freshnessValidatedDate: never
 ---

src/content/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing.mdx

@@ -91,11 +91,11 @@ Here's a table with comparisons of the two options. Prices and limits are monthl
       </td>
 
       <td>
-        $0.35/GB Ingested
+        $0.40/GB Ingested
       </td>
 
       <td>
-        $0.55/GB Ingested
+        $0.60/GB Ingested
       </td>
 
       <td/>

src/content/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts.mdx

@@ -334,11 +334,11 @@ Here are some query recommendations for helping you understand the estimated cos
     SELECT latest(GigabytesIngestedBillable) * YOUR_PER_GB_COST
     ```
 
-    Here's an example of this query using a [per-GB cost of $0.35](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing/#data-prices):
+    Here's an example of this query using a [per-GB cost of $0.40](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing/#data-prices):
 
     ```sql
     FROM NrMTDConsumption 
-    SELECT latest(GigabytesIngestedBillable) * .35
+    SELECT latest(GigabytesIngestedBillable) * .40
     ```
   </Collapser>
 

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

@@ -113,6 +113,42 @@ 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.
 
+### Best practices for optimizing your knowledge source content
+To maximize the effectiveness of New Relic AI's ability to surface relevant information, provide accurate answers, and accelerate incident resolution, it's crucial to structure your internal documentation with the AI in mind. While these guidelines focus on incident retro documents for quick and efficient incident management, the principles apply broadly to other knowledge types. The knowledge connector performs best when your source documents are clear, consistent, and rich in specific details relevant to their intended use.
+
+Follow these best practices when creating and maintaining your retro documents and other knowledge base articles to ensure New Relic AI can optimally leverage the indexed information:
+
+- **Descriptive title:** Ensure each document has a clear and descriptive title. This helps New Relic AI fetch the closest matching content based on alert titles and user queries. For example, "Memory Leak in Service X during v2.3 Deployment" is more effective than "System Slowdown."
+
+- **Incident summary:** Begin retro documents with a brief, high-level summary of the incident.
+
+- **Customer impact details:** Include specific details about the customer impact (for example, number of affected users, services degraded, financial impact) to help first responders and the AI gauge severity.
+
+- **Entities affected and downstream entities:** Document the specific services, microservices, databases, or other infrastructure entities directly affected by an issue, as well as any known downstream entities impacted.
+
+- **Why did it happen (root causes):** Clearly articulate the identified root cause(s) of an issue, avoiding ambiguity. Be specific. For example, "Memory leak due to recent deployment v2.3" is more effective than "System became slow."
+
+- **Mitigating actions:** Detail the specific, actionable steps taken to mitigate and ultimately resolve an issue. This allows New Relic AI to suggest proven fixes for similar future issues.
+
+- **Future prevention:** Outline long-term prevention strategies, follow-up tasks, and improvements identified to avoid recurrence of similar issues.
+
+- **Tag related entities/services:** While direct entity impact in RAG is an evolving feature, tagging related entities and services within your document is crucial for future enhancements to accurately surface the right blast radius and relevant information.
+
+- **Teams involved (who fixed it):** List the specific teams or departments who worked on an issue, especially those who played a crucial role in diagnosis or resolution. This helps New Relic AI direct first responders to the right experts.
+
+- **When did it happen:** Include the precise timestamp of an incident's start.
+
+- **Which alert triggered it:** Specify the exact alert or condition that initially triggered an incident response.
+
+- **How long was the incident:** Document the duration of the incident from detection to resolution.
+
+- **Participants in incident:** List individuals who actively participated in the incident resolution process.
+
+- **Owning team:** Clearly identify the team responsible for the service or component where the incident originated or the team owning the resolution.
+
+- **Regularly update and review:** Ensure your knowledge connector is configured to run on a recurring basis, and make it a practice to regularly review and update your source documents. This ensures New Relic AI always has access to the most up-to-date and accurate information.
+
+
 To start indexing Confluence content, you need:
 
 - Confluence URL with your unique Confluence cloud ID: https://api.atlassian.com/ex/confluence/[cloud_id]
@@ -123,7 +159,7 @@ To start indexing Confluence content, you need:
   - `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 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 these mentioned steps:
 
 <Steps>
 

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

@@ -170,16 +170,16 @@ This page describes limits and rules pertaining to New Relic <InlinePopover type
 
     </td>
       <td>
-        [Targets (product entities)](/docs/new-relic-solutions/get-started/glossary/#alert-target) per condition
+        [Facets](/docs/new-relic-solutions/get-started/glossary/#facet) per condition
       </td>
 
       <td>
-        1 target
+        N/A
       </td>
 
       <td>
-        20K targets for NRQL conditions
-        1K targets for non-NRQL conditions
+        * 20K facets for NRQL conditions
+        * 1K facets for non-NRQL conditions
       </td>
     </tr>
 
@@ -274,7 +274,21 @@ This page describes limits and rules pertaining to New Relic <InlinePopover type
         </Callout>
       </td>
     </tr>
+    <tr>
+      <td>
 
+      </td>
+      <td>
+        Alert events per condition threshold
+      </td>
+      <td>
+        N/A
+      </td>
+      <td>
+        1K per minute
+      </td>
+
+    </tr>
     <tr>
       <td id="workflows">
       Workflows

src/content/docs/apis/nerdgraph/examples/nerdgraph-scorecards-tutorial.mdx

@@ -24,10 +24,10 @@ This tutorial provides examples of how to use NerdGraph to manage Scorecards and
 New Relic provides various NerdGraph mutations to create and manage Scorecards and related rules.
 
 <CollapserGroup>
-<Collapser 
+<Collapser
     id="fetch-organization-id"
     title="Fetch your organization ID">
-    
+
     For managing Scorecards and rules, you need to provide your organization ID. You can retrieve your organization ID using the `actor` query.
     #### Sample request
 
@@ -41,10 +41,10 @@ New Relic provides various NerdGraph mutations to create and manage Scorecards a
   }
 ```
   </Collapser>
-  <Collapser 
+  <Collapser
     id="create-scorecard"
     title="Create a Scorecard">
-    
+
     You can create your own Scorecard using the `entityManagementCreateScorecard` mutation.
 
     #### Input parameters
@@ -104,7 +104,7 @@ New Relic provides various NerdGraph mutations to create and manage Scorecards a
 ```
   </Collapser>
 
-  <Collapser 
+  <Collapser
     id="create-rule"
     title="Create a rule">
 
@@ -146,6 +146,12 @@ You can create a new rule for a Scorecard using the `entityManagementCreateScore
       <td>Yes</td>
       <td>List of account IDs where the rule should execute the query.</td>
     </tr>
+    <tr>
+      <td>`joinAccounts`</td>
+      <td>Int</td>
+      <td>No</td>
+      <td>List of account IDs that need to be joined with each account where the query is executed.</td>
+    </tr>
     <tr>
       <td>`organizationId`</td>
       <td>String (ID)</td>
@@ -158,14 +164,15 @@ You can create a new rule for a Scorecard using the `entityManagementCreateScore
 #### Sample request
 
 ```graphql
-  mutation CreateRule($name: String!, $description: String, $query: String!, $accounts: [Int!]!, $organizationId: ID!) {
+  mutation CreateRule($name: String!, $description: String, $query: String!, $accounts: [Int!]!, $joinAccounts: [Int!], $organizationId: ID!) {
     entityManagementCreateScorecardRule(
       scorecardRuleEntity: {
         name: $name,
         description: $description
         enabled: true,
         nrqlEngine: {
           accounts: $accounts,
+          joinAccounts: $joinAccounts,
           query: $query
         },
         scope: {id: $organizationId, type: ORGANIZATION}}
@@ -179,12 +186,13 @@ You can create a new rule for a Scorecard using the `entityManagementCreateScore
   {
     "name": "APM Services Have Alerts Defined",
     "description": "Check that APM services have alerts associated with them",
+    "accounts": [1, 2, 3],
     "query": "SELECT if(latest(alertSeverity) != 'NOT_CONFIGURED', 1, 0) as 'score' FROM Entity WHERE type = 'APM-APPLICATION' AND tags.nr.team IS NOT NULL AND tags.environment IS NOT NULL FACET id as 'entityGuid', tags.nr.team as 'team', tags.environment as 'environment' LIMIT MAX SINCE 1 day ago",
     "organizationId": "xxxxxxxx-yyyy-0000-aaaa-0123456789qwe"
   }
   ```
   </Collapser>
-  <Collapser 
+  <Collapser
     id="add-rule"
     title="Add a rule to a Scorecard">
 
@@ -232,10 +240,10 @@ You can associate a rule with a Scorecard using the `entityManagementAddCollecti
     "rules": [] // Provide list of all rule ids which are generated during rule creation.
   }
 ```
-  
+
   </Collapser>
 
-  <Collapser 
+  <Collapser
     id="update-scorecard"
     title="Update a Scorecard">
 
@@ -293,8 +301,8 @@ mutation UpdateScorecard($id: ID!, $description: String, $name: String!) {
 }
 ```
   </Collapser>
-  
-  <Collapser 
+
+  <Collapser
     id="update-rule"
     title="Update a rule">
 
@@ -342,6 +350,12 @@ You can update a rule for the Scorecard using the `entityManagementUpdateScoreca
       <td>Yes</td>
       <td>List of account IDs where the rule should execute the query.</td>
     </tr>
+    <tr>
+      <td>`joinAccounts`</td>
+      <td>Int</td>
+      <td>No</td>
+      <td>List of account IDs that need to be joined with each account where the query is executed.</td>
+    </tr>
     <tr>
       <td>`enabled`</td>
       <td>Boolean</td>
@@ -354,25 +368,26 @@ You can update a rule for the Scorecard using the `entityManagementUpdateScoreca
 #### Sample request
 
 ```graphql
-  mutation UpdateRule($ruleId: ID!, $name: String!, $description: String, $query: String!, $queryAccounts: [Int!]!, $enabled: Boolean) {
+  mutation UpdateRule($ruleId: ID!, $name: String!, $description: String, $query: String!, $queryAccounts: [Int!]!, $joinAccounts: [Int!], $enabled: Boolean) {
     entityManagementUpdateScorecardRule(
       id: $ruleId
-      scorecardRuleEntity: {description: $description, name: $name, enabled: $enabled, nrqlEngine: {accounts: $queryAccounts, query: $query}}
+      scorecardRuleEntity: {description: $description, name: $name, enabled: $enabled, nrqlEngine: {accounts: $queryAccounts, joinAccounts: $joinAccounts, query: $query}}
     ) {
       entity {
         id
         name
         description
         nrqlEngine {
           accounts
+          joinAccounts
           query
         }
       }
     }
   }
 ```
   </Collapser>
-  <Collapser 
+  <Collapser
     id="delete-scorecard"
     title="Delete a Scorecard or Rule">
 
@@ -418,7 +433,7 @@ mutation DeleteEntity($id: ID!) {
 
 <CollapserGroup>
 
-  <Collapser 
+  <Collapser
     id="fetch-scorecards"
     title="Get rules in a Scorecard">
 
@@ -465,8 +480,8 @@ You can retrieve all rules associated with a specific Scorecard using the `Fetch
   }
 ```
   </Collapser>
-  
-  <Collapser 
+
+  <Collapser
     id="fetch-rule"
     title="Retrieve Scorecard Details Associated with a Rule">
 
@@ -509,6 +524,7 @@ You can retrieve the details of collection using the `FetchRulesCollection` quer
               name
               nrqlEngine {
                 accounts
+                joinAccounts
                 query
               }
             }