Merge pull request #22609 from newrelic/daily-release/02-01-26-morningg

Daily release/02 01 26 morningg

Author: WriteMayur

src/content/docs/apis/nerdgraph/examples/nerdgraph-manage-groups.mdx

@@ -276,45 +276,14 @@ Here's an example response:
 
 ## Create a role [#create-role]
 
-Here's an example of creating a [role](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts/#roles):
-
-```graphql
-mutation {
-  customRoleCreate(
-    container: {
-      id: "YOUR_ORGANIZATION_ID"
-      type: "ORGANIZATION"
-    }
-    name: "MY CUSTOM ROLE"
-    permissionIds: [1, 2, 3] 
-    scope: "account" 
-  ) {
-    id
-  }
-}
-```
-### Parameters
-- `container`:
-  - `id`: (String) The unique identifier of your organization. Replace `YOUR_ORGANIZATION_ID` with your actual organization ID.
-  - `type`: (String) The type of container. Currently, the only supported type is `"ORGANIZATION"`.
-  - `name`: (String) The name assigned to the custom role. Example: `"MY CUSTOM ROLE"`.
-- `permissionIds`: (Array) A list of permission IDs representing the capabilities assigned to the custom role. Ensure these IDs correspond to valid permissions in your system.
-- `scope`: (String) The level at which the role's permissions apply. In this instance, the scope is `"ACCOUNT"`.
-
-### Response
-- `id`: Returns the unique ID of the newly created custom role.
-
-    <Callout variant="important">
-      - Replace `YOUR_ORGANIZATION_ID` with your specific organization ID before executing the mutation.
-      - Ensure that the `permissionIds` provided are valid and align with the permissions you want to grant.
-    </Callout>
-
 Before you create a custom role, you have to identify the permissions you want to assign to it.
 
-Use the following query to retrieve the list of permissions:
+### Retrieve permission IDs
+
+Use the following query to retrieve the list of account-scoped permissions:
 
 ```graphql
-mutation {
+query {
   customerAdministration {
     permissions {
       items {
@@ -329,10 +298,11 @@ mutation {
   }
 }
 ```
-This returns account-scoped permissions. For permissions scoped to an org, run the following query instead:
+
+For permissions scoped to an organization, run the following query instead:
 
 ```graphql
-{
+query {
   customerAdministration {
     permissions(filter: {scope: {eq: "organization"}}) {
       items {
@@ -356,7 +326,41 @@ Note the following fields:
   - `product`: (String) The product that the permission applies to.
   - `subsetIds`: (Array) A list of IDs representing subsets or related permissions.
 
-After you have the unique identifier for each permission you want to assign to the new role, create that role.
+### Create the custom role
+
+After you have the unique identifier for each permission you want to assign to the new role, use the following mutation to create a [role](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts/#roles):
+
+```graphql
+mutation {
+  customRoleCreate(
+    container: {
+      id: "YOUR_ORGANIZATION_ID"
+      type: "ORGANIZATION"
+    }
+    name: "MY CUSTOM ROLE"
+    permissionIds: [1, 2, 3]
+    scope: "account"
+  ) {
+    id
+  }
+}
+```
+
+### Parameters
+- `container`:
+  - `id`: (String) The unique identifier of your organization. Replace `YOUR_ORGANIZATION_ID` with your actual organization ID.
+  - `type`: (String) The type of container. Currently, the only supported type is `"ORGANIZATION"`.
+  - `name`: (String) The name assigned to the custom role. Example: `"MY CUSTOM ROLE"`.
+- `permissionIds`: (Array) A list of permission IDs representing the capabilities assigned to the custom role. Use the IDs retrieved from the permissions query above.
+- `scope`: (String) The level at which the role's permissions apply. In this instance, the scope is `"ACCOUNT"`.
+
+### Response
+- `id`: Returns the unique ID of the newly created custom role.
+
+    <Callout variant="important">
+      - Replace `YOUR_ORGANIZATION_ID` with your specific organization ID before executing the mutation.
+      - Replace the example `permissionIds: [1, 2, 3]` with the actual permission IDs you retrieved from the permissions query.
+    </Callout>
 
 ## Update role [#update-role]
 

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

@@ -41,7 +41,47 @@ If you don't have one already, [create a New Relic account](https://newrelic.com
       </td>
 
       <td>
-        UNIX-like operating systems including Linux, Solaris, FreeBSD, and macOS. The Python agent does not support Windows environments.
+          The Python agent is compatible with these OS:
+
+          * Linux
+          * macOS
+          * Windows Server 2012 or higher (Python 3.13 and higher required)
+          * Windows 10 or higher (Python 3.13 and higher required)
+          * Other UNIX-like operating systems including:
+            * Solaris
+            * FreeBSD
+      </td>
+    </tr>
+
+    <tr>
+      <td>
+        Architectures
+      </td>
+
+      <td>
+          The Python agent supports the following architectures:
+
+          * x86-64 (amd64)
+          * ARM64 (aarch64)
+      </td>
+    </tr>
+
+    <tr>
+      <td>
+        Prebuilt Binaries
+      </td>
+
+      <td>
+          The Python agent has prebuilt binaries for the following environments:
+
+          * Linux
+            * x86-64 (amd64)
+            * ARM64 (aarch64)
+          * Windows (Python 3.13 and higher)
+            * x86-64 (amd64)
+            * ARM64 (aarch64)
+
+          The Python agent may work on other architectures and operating systems when built from source, but some features may not be available.
       </td>
     </tr>
 
@@ -55,6 +95,11 @@ If you don't have one already, [create a New Relic account](https://newrelic.com
 
         Recommendation: Use Python version 3.8 or higher with our agent.
 
+        <Callout variant="tip">
+          Python 3.13 or higher is required for Windows operating systems.
+        </Callout>
+
+
         * Python versions 2.6 and 3.3 are supported only by Python agent versions 3.4.0.95 or lower.
         * Python version 3.4 is supported only by Python agent versions 4.20.0.120 or lower.
         * Python version 3.5 is supported only by Python agent versions 5.24.0.153 or lower.
@@ -179,15 +224,15 @@ The following are proposed time ranges. The actual release date may vary.
   <tbody>
     <tr>
       <td>
-        3.14
+        3.15
       </td>
 
       <td>
-        October 2025
+        October 2026
       </td>
 
       <td>
-        November 2025
+        November 2026
       </td>
     </tr>
   </tbody>

src/content/docs/nrql/using-nrql/schedule-nrql-searches.mdx

@@ -18,7 +18,7 @@ Scheduled NRQL searches solve this problem by automating your repetitive queries
 <Callout title="preview">
   We're still working on this feature, but we'd love for you to try it out!
 
-  This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). During the preview period, this feature is only available to customers running New Relic in the US data centers and is accessible through the [Logs UI](/docs/logs/ui-data/use-logs-ui), with plans to expand to other capabilities after general availability.
+  This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). During the preview period, this feature is accessible through the [Logs UI](/docs/logs/ui-data/use-logs-ui), with plans to expand to other capabilities after general availability.
 </Callout>
 
 ## What you can do [#features]

src/content/docs/service-architecture-intelligence/catalogs/catalogs.mdx

@@ -14,21 +14,21 @@ New Relic Catalogs provides a single-pane view that enhances the observability a
 
 With Catalogs, you can quickly identify and focus on the most relevant information, ensuring easy access to what matters most. It serves as the single source of truth, enabling users to discover, manage, and optimize their systems with confidence.
 
-By consolidating data from multiple sources—including <DNT>[Teams](/docs/service-architecture-intelligence/teams/teams)</DNT>, <DNT>[Scorecards](/docs/service-architecture-intelligence/scorecards/getting-started)</DNT>, <DNT>[Maps](/docs/service-architecture-intelligence/maps/advanced-maps/)</DNT>, and <DNT>[repository](/docs/codestream/observability/repo-association/)</DNT> into a single interface, Catalogs replaces the <DNT>All Entities</DNT> view, offering a more structured and insightful experience. It provides a comprehensive overview of high-value entities, enriched with detailed metadata and actionable insights, helping teams stay aligned and efficient.
+By consolidating data from multiple sources—including <DNT>[Teams](/docs/service-architecture-intelligence/teams/teams)</DNT>, <DNT>[Scorecards](/docs/service-architecture-intelligence/scorecards/getting-started)</DNT>, <DNT>[Maps](/docs/service-architecture-intelligence/maps/advanced-maps/)</DNT>, and repository into a single interface, Catalogs replaces the <DNT>All Entities</DNT> view, offering a more structured and insightful experience. It provides a comprehensive overview of high-value entities, enriched with detailed metadata and actionable insights, helping teams stay aligned and efficient.
 
 
 
 ## Key features [#features]
 
--  Unified view: Catalogs is integrated with various sources such as <DNT>[Teams](/docs/service-architecture-intelligence/teams/teams)</DNT>, <DNT>[Scorecards](/docs/service-architecture-intelligence/scorecards/getting-started)</DNT>, <DNT>[Maps](/docs/service-architecture-intelligence/maps/advanced-maps/)</DNT>, and <DNT>[repository](/docs/codestream/observability/repo-association/)</DNT> into a single cohesive interface. This displays high-value entity types with detailed metadata including golden metrics and insights to provide a deeper understanding of system status.
+-  Unified view: Catalogs is integrated with various sources such as <DNT>[Teams](/docs/service-architecture-intelligence/teams/teams)</DNT>, <DNT>[Scorecards](/docs/service-architecture-intelligence/scorecards/getting-started)</DNT>, <DNT>[Maps](/docs/service-architecture-intelligence/maps/advanced-maps/)</DNT>, and repository into a single cohesive interface. This displays high-value entity types with detailed metadata including golden metrics and insights to provide a deeper understanding of system status.
 
--  Personalized experience: <DNT>Applications Catalog</DNT> allows users to customize their view to focus on the most relevant content. This helps users to streamline workflows and enhance productivity.
+-  Personalized experience: Allows users to customize their view to focus on the most relevant content. This helps users to streamline workflows and enhance productivity.
 
--  Seamless integration: <DNT>Applications Catalog</DNT> connects users with other New Relic capabilities to allow them to explore data in depth and gain a thorough understanding of entities. 
+-  Seamless integration: Connects users with other New Relic capabilities to allow them to explore data in depth and gain a thorough understanding of entities. 
 
-- Ownership: <DNT>Catalogs</DNT> displays entity ownership information in the <DNT>Teams</DNT> column. Hover over the <DNT>Teams</DNT> link for more information, or click it to visit the <DNT>Teams Hub</DNT> page. For more information, see <DNT>[Teams](/docs/service-architecture-intelligence/teams/teams)</DNT>.
+-  Ownership: Displays entity ownership information in the <DNT>Teams</DNT> column. Hover over the <DNT>Teams</DNT> link for more information, or click it to visit the <DNT>Teams Hub</DNT> page. For more information, see <DNT>[Teams](/docs/service-architecture-intelligence/teams/teams)</DNT>.
 
-- Score: <DNT>Applications Catalog</DNT> is integrated with Scorecards to show how your entities are performing against company-defined best practices. For more information, see <DNT>[Scorecards](/docs/service-architecture-intelligence/scorecards/getting-started)</DNT>.
+-  Score: Integrates with Scorecards to show how your entities are performing against company-defined best practices. For more information, see <DNT>[Scorecards](/docs/service-architecture-intelligence/scorecards/getting-started)</DNT>.
 
 
 ## Getting started [#getting-started]

src/content/docs/service-architecture-intelligence/catalogs/infrastructure-catalog.mdx

@@ -119,41 +119,15 @@ The Infrastructure catalog is available in the New Relic platform, providing a c
         </tr>
         <tr>
             <td>Region</td>
-            <td>The geographic location or cloud provider region where the resource is deployed. This helps you understand data locality, latency, and compliance. The Region value is populated automatically by checking for values across a prioritized list of metadata tags. The first non-empty value found is used, which ensures consistent classification even when naming conventions vary. 
-            The following tags are checked in order: 
-            <ul>
-                <li>`region`</li>
-                <li>`cloud.region`</li>
-                <li>`aws.awsRegion`</li>
-                <li>`azure.regionName`</li>
-                <li>`gcp.region`</li>
-            </ul>
-            </td>
+            <td>The geographic location or cloud provider region where the resource is deployed. This helps you understand data locality, latency, and compliance.</td>
         </tr>
         <tr>
             <td>Availability Zone</td>
-            <td>The isolated location within a cloud region where the resource is deployed. This is used for fault tolerance and high availability by distributing resources across multiple zones. The first non-empty value found is used, which ensures consistent classification even when naming conventions vary. 
-            The following tags are checked in order: 
-            <ul>
-                <li>`availabilityZone`</li>
-                <li>`cloud.availability_Zone`</li>
-                <li>`aws.availabilityZone`</li>
-                <li>`awsAvailabilityZone`</li>
-                <li>`azure.availabilityZone`</li>
-                <li>`gcp.zone`</li>
-            </ul>
-            </td>
+            <td>The isolated location within a cloud region where the resource is deployed. This is used for fault tolerance and high availability by distributing resources across multiple zones.</td>
         </tr>
         <tr>
             <td>Environment</td>
-            <td>The stage or purpose of the resource in the software lifecycle. For example, `development`, `staging`, or `production`. This helps teams manage stability, testing, and deployment workflows. The first non-empty value found is used, which ensures consistent classification even when naming conventions vary. 
-            The following tags are checked in order: 
-            <ul>
-                <li>`Environment`</li>
-                <li>`environment`</li>
-                <li>`env`</li>
-            </ul>
-            </td>
+            <td>The stage or purpose of the resource in the software lifecycle. For example, `development`, `staging`, or `production`. This helps teams manage stability, testing, and deployment workflows.</td>
         </tr>
     </tbody>
 </table>

src/content/docs/service-architecture-intelligence/getting-started.mdx

@@ -1,31 +1,25 @@
 ---
 title: "Getting Started with Service Architecture Intelligence"
 metaDescription: "Learn more about Service Architecture Intelligence in New Relic One."
-tags: ["service architecture intelligence", "New Relic One", "service catalog", "scorecards", "catalog", "inventory catalog", "repository catalog", "team"]
+tags: ["service architecture intelligence", "New Relic One", "service catalog", "scorecards", "catalog", "inventory catalog", "repository catalog", "infrastructure catalog", "team"]
 freshnessValidatedDate: never
 ---
 
 
-<Callout title="preview">
-    We're still working on this feature, but we'd love for you to try it out!
-
-    This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy).
-</Callout>
-
-
 Service Architecture Intelligence provides a centralized view of your organization's services and operations. It enhances productivity by offering tools for effective resource management, operational optimization, and compliance assurance. The Service Architecture Intelligence has integrated various capabilities, including team management, system observability, performance evaluation, and infrastructure visualization, to streamline processes and improve collaboration across teams.
 
 ## Capabilities [#capabilities]
 
 The Service Architecture Intelligence offers the following capabilities:
 
-- [Team](/docs/service-architecture-intelligence/teams/teams): New Relic Teams connects the entities you monitor to the teams that own them. This feature allows you to create or import teams into the New Relic platform, assign entities to teams, and manage team-related tasks efficiently. 
+- [Teams](/docs/service-architecture-intelligence/teams/teams): New Relic Teams connects the entities you monitor to the teams that own them. This feature allows you to create or import teams into the New Relic platform, assign entities to teams, and manage team-related tasks efficiently. 
 
 - [Catalogs](/docs/service-architecture-intelligence/catalogs/catalogs): New Relic Catalogs provide centralized inventories of high-value entities, complete with details such as ownership, health, and compliance status. Use Catalogs to gain an understanding of your system's health, identify areas for improvement, and take steps to enhance performance within a unified platform. 
 
     - [Applications catalog:](/docs/service-architecture-intelligence/catalogs/applications-catalog) The Application Catalog presents a consolidated view of application entities, aiding in the observability and management of applications across your organization. This unified perspective supports informed decision-making, helps to streamline workflows, and fosters team collaboration.
-    - [Repository catalog:](/docs/service-architecture-intelligence/catalogs/repositoryCatalog) The Repository Catalog consolidates the oversight of an organization's repositories, promoting transparency and cooperation among teams. It provides stakeholders with the means to efficiently locate and understand repositories, their contents, and their status, as well as to identify ownership. 
+    - [Repository catalog:](/docs/service-architecture-intelligence/catalogs/repository-catalog) The Repository Catalog consolidates the oversight of an organization's repositories, promoting transparency and cooperation among teams. It provides stakeholders with the means to efficiently locate and understand repositories, their contents, and their status, as well as to identify ownership.
+    - [Infrastructure catalog:](/docs/service-architecture-intelligence/catalogs/infrastructure-catalog) The Infrastructure Catalog provides a complete inventory of all your infrastructure entities. Use it to manage resources, accelerate root cause analysis, and identify observability gaps.
 
 - [Scorecards:](/docs/service-architecture-intelligence/scorecards/getting-started) New Relic Scorecards evaluate team or group performance against predefined rules and custom metrics. They provide a standardized and structured approach to software development, helping organizations adhere to a well-defined engineering strategy. 
 
-- [Maps:](/docs/service-architecture-intelligence/maps/advanced-maps) The new map experience provides a unified and integrated view of your cloud estate, allowing seamless navigation and exploration of services and infrastructure. It integrates tracing, infrastructure, and performance data into a cohesive experience, addressing limitations of the previous service map.
+- [Maps:](/docs/service-architecture-intelligence/maps/advanced-maps) The new map experience provides a unified and integrated view of your cloud estate, allowing seamless navigation and exploration of services and infrastructure. It integrates tracing, infrastructure, and performance data into a cohesive experience, addressing limitations of the previous service map.