more requested edits

wajihaparvez · wajihaparvez · commit 9df2bbf87f80 · 2025-07-28T14:38:49.000-04:00
diff --git a/deploy-manage/cloud-connect.md b/deploy-manage/cloud-connect.md
@@ -46,7 +46,7 @@ No. The currently available functionality does not consume ECU, but this may cha
 
 $$$cc-data$$$
 
-Yes. For AutoOps, the Elastic Agent only sends cluster metrics to {{ecloud}}, not the underlying data within your cluster. Learn more about the [collected metrics](/deploy-manage/monitor/autoops/cc-collected-metrics.md).
+Yes. For AutoOps, the Elastic Agent only sends cluster metrics to {{ecloud}}, not the underlying data within your cluster. Learn more in [](/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md). 
 :::
 
 :::{dropdown} Are more services going to be available with Cloud Connect?
diff --git a/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md b/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md
@@ -18,6 +18,5 @@ In this section, you'll find the following information:
 * How to [connect your self-managed cluster to AutoOps](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md).
 * How to [manage your connected clusters](/deploy-manage/monitor/autoops/cc-manage-connected-clusters.md).
 * How to [manage users of your connected clusters](/deploy-manage/monitor/autoops/cc-manage-users.md).
-* The [metrics](/deploy-manage/monitor/autoops/cc-collected-metrics.md) that are collected when you connect your self-managed cluster to AutoOps.
 * [FAQs](/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md) about AutoOps for self-managed clusters.
 * A [troubleshooting guide](/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md) to help you with any issues you may encounter.
diff --git a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md
@@ -11,8 +11,6 @@ Find answers to your questions about AutoOps for self-managed clusters.
 
 :::{dropdown} Why should I use AutoOps for my self-managed cluster?
 
-$$$cc-autoops-why$$$
-
 AutoOps simplifies the operation of your {{es}} clusters by providing real-time monitoring, performance insights, and issue detection. It helps you identify and resolve problems like ingestion bottlenecks and unbalanced shards, reducing manual effort and preventing performance issues. 
 
 When you need support, AutoOps gives the Elastic team real-time visibility into your cluster, leading to faster resolutions. 
@@ -22,29 +20,21 @@ Using AutoOps for your self-managed cluster lets you access all these features w
 
 :::{dropdown} Which versions of {{es}} does AutoOps support?
 
-$$$cc-autoops-es-version$$$
-
 AutoOps is compatible with all [supported {{es}} versions](https://www.elastic.co/support/eol).
 :::
 
 :::{dropdown} Which deployment types can be connected to AutoOps?
 
-$$$cc-autoops-deployment-types$$$
-
 You can connect to AutoOps on a standalone Elastic Stack, ECE (Elastic Cloud Enterprise), or ECK (Elastic Cloud on Kubernetes) deployment.
 :::
 
 :::{dropdown} Can I use AutoOps for self-managed clusters if my environment is air-gapped?
 
-$$$cc-autoops-air-gapped$$$
-
 Not at this time. AutoOps is currently only available as a cloud service and you need an internet connection to send metrics to the {{ecloud}}. For air-gapped environments, we plan to offer a locally deployable version in the future.
 :::
 
 :::{dropdown} Do I have to define an Elastic IP address to enable the agent to send data to the {{ecloud}}?
 
-$$$cc-autoops-elastic-ip$$$
-
 You may need to define an IP address if your organization’s settings will block the agent from sending out data. 
 
 To enable IP ranges, {{ecloud}} offers a selection of static IP addresses. All traffic directed to {{ecloud}} deployments, whether originating from the public internet, your private cloud network through the public internet, or your on-premise network through the public internet utilizes Ingress Static IPs as the network destination. 
@@ -54,18 +44,27 @@ For more information, refer to [](/deploy-manage/security/elastic-cloud-static-i
 
 :::{dropdown} Where are AutoOps metrics stored, and does it cost extra to ship metrics to the {{ecloud}}?
 
-$$$cc-autoops-collected-metrics$$$
-
 You can choose the CSP and region in which your cluster metrics will be stored from a list of [available regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md). 
 
 Shipping metrics to the {{ecloud}} may come at an additional cost. For example, when sending metrics data from your cluster in a CSP region to the {{ecloud}}, shipping costs will be determined by your agreement with that CSP.
 :::
 
 :::{dropdown} What information does the Elastic Agent extract from my cluster?
 
-$$$cc-autoops-collected-metrics$$$
-
-The Elastic Agent only extracts cluster metrics and sends them to the {{ecloud}}. For a list of these metrics, refer to [](/deploy-manage/monitor/autoops/cc-collected-metrics.md).
+The Elastic Agent only extracts and sends cluster metrics to the {{ecloud}}, not the underlying data within your cluster. The following metrics are collected:
+
+| API | Description | Collected data |
+| --- | --- | --- |
+| [_cat/shards](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cat-shards) | Returns detailed information about the shards within the cluster | Shard states, node allocation, index names, sizes, and replica information |
+| [_nodes/stats](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-nodes-stats) | Retrieves statistics from cluster nodes including JVM, OS, process, and transport metrics | CPU usage, memory utilization, thread pools, file system stats |
+| [_cluster/settings](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-get-settings) | Returns the settings configured for the cluster | Persistent and transient settings such as cluster-wide configurations |
+| [_cluster/health](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-health) | Provides information about the overall health of the cluster | Status (green/yellow/red), number of nodes, number of shards |
+| [_cat/template](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cat-templates) | Lists all index templates in the cluster | Template names, patterns, and basic settings |
+| [_index_template](/manage-data/data-store/templates.md) | Retrieves composable index templates | Index settings, mappings, and aliases |
+| [_component_template](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-get-component-template) | Fetches component templates used for building index templates | Metadata for re-usable mappings and settings |
+| [_tasks](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-tasks) | Displays information about currently running tasks on the cluster | Task descriptions, start times, running nodes, and execution details |
+| [_template](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-get-template) | Retrieves legacy index templates | Similar to composable index templates but in older format |
+| [_resolve/index/*](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-resolve-index) | Resolves index, data stream, and alias names to their current definitions | Mappings between names and underlying data objects |
 :::
 
 
diff --git a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md
@@ -13,24 +13,18 @@ Use this guide to troubleshoot any issues you may encounter when using AutoOps f
 
 :::{dropdown} I’m trying to create a Cloud organization, but I’m already part of a different one.
 
-$$$cc-autoops-existing-cloud-org$$$
-
 :::{include} /deploy-manage/monitor/_snippets/single-cloud-org.md
 :::
 
 :::
 
 :::{dropdown} I need to uninstall Elastic Agent.
 
-$$$cc-autoops-uninstall-agent$$$
-
 Refer to [](/solutions/security/configure-elastic-defend/uninstall-elastic-agent.md) for instructions.
 :::
 
 :::{dropdown} My self-managed cluster was disconnected from the {{ecloud}} and I want to reconnect it.
 
-$$$cc-autoops-reconnect-cluster$$$
-
 If the cluster was disconnected by one of the users in your Cloud organization, you can simply repeat the [installation process](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md) to reconnect. If not, explore [additional resources](/troubleshoot/index.md#troubleshoot-additional-resources) or [contact us](/troubleshoot/index.md#contact-us).
 
 :::{include} /deploy-manage/monitor/_snippets/disconnect-cluster.md
@@ -40,8 +34,6 @@ If the cluster was disconnected by one of the users in your Cloud organization,
 
 :::{dropdown} After running the installation command, I can't move on to the next steps.
 
-$$$cc-autoops-command-error$$$
-
 If an error appears on the screen, follow the suggestion in the error message and try to run the command again. If the issue is not resolved, explore [additional resources](/troubleshoot/index.md#troubleshoot-additional-resources) or [contact us](/troubleshoot/index.md#contact-us).
 :::
 
diff --git a/deploy-manage/monitor/autoops/cc-collected-metrics.md b/deploy-manage/monitor/autoops/cc-collected-metrics.md
@@ -16,7 +16,7 @@ When you connect your self-managed cluster to AutoOps on {{ecloud}}, the followi
 | [_cluster/settings](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-get-settings) | Returns the settings configured for the cluster | Persistent and transient settings such as cluster-wide configurations |
 | [_cluster/health](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-health) | Provides information about the overall health of the cluster | Status (green/yellow/red), number of nodes, number of shards |
 | [_cat/template](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cat-templates) | Lists all index templates in the cluster | Template names, patterns, and basic settings |
-| [_index_template](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cat-templates) | Retrieves composable index templates | Index settings, mappings, and aliases |
+| [_index_template](/manage-data/data-store/templates.md) | Retrieves composable index templates | Index settings, mappings, and aliases |
 | [_component_template](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-get-component-template) | Fetches component templates used for building index templates | Metadata for re-usable mappings and settings |
 | [_tasks](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-tasks) | Displays information about currently running tasks on the cluster | Task descriptions, start times, running nodes, and execution details |
 | [_template](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-get-template) | Retrieves legacy index templates | Similar to composable index templates but in older format |
diff --git a/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md b/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md
@@ -20,11 +20,10 @@ Ensure you meet the following requirements before proceeding:
 * The agent you install for the connection is allowed to send metrics outside your organization to {{ecloud}}.
 * You have a dedicated user with following permissions to set up the Elastic Agent:
 
-    | Type | Privilege |
+    | Setting | Privileges |
     | --- | --- |
-    | Cluster | `monitor`, `read_ilm`, and `read_slm` |
-    | Index | `monitor`, `view_index_metadata`, and `*` indices <br> `allow_restricted_indices`: `true` |
-    | Index | `read` and `.kibana*` indices <br> `allow_restricted_indices`: `true` |
+    | Cluster privileges | `monitor`, `read_ilm`, and `read_slm` |
+    | Index privileges | `*` indices: `monitor`, `view_index_metadata` <br><br> `.kibana*` indices: `read`  |
 
 ## Connect to AutoOps
 
@@ -102,10 +101,12 @@ Complete the following steps to run the command:
 
 5. Return to the wizard and select **I have run the command**.
 
-It may take a few minutes for your cluster details to be validated and the first metrics to be shipped to AutoOps. For details on which metrics are collected by the agent, refer to [](/deploy-manage/monitor/autoops/cc-collected-metrics.md).
+It may take a few minutes for your cluster details to be validated and the first metrics to be shipped to AutoOps.
 
 If the connection is unsuccessful, an error message will appear with a possible reason for the failure and recommended next steps. For a list of these errors, refer to [Potential errors](/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md#potential-errors).
 
+Sometimes, an exact reason for the failure cannot be determined. In this case, explore [additional resources](/troubleshoot/index.md#troubleshoot-additional-resources) or [contact us](/troubleshoot/index.md#contact-us).
+
 ### Launch AutoOps
 
 If the connection is successful, AutoOps will start analyzing your metrics and reporting on any issues found. Depending on the size of your cluster, this process can take up to 30 minutes. 
diff --git a/deploy-manage/toc.yml b/deploy-manage/toc.yml
@@ -675,7 +675,6 @@ toc:
           - hidden: monitor/autoops/cc-connect-self-managed-to-autoops.md
           - hidden: monitor/autoops/cc-manage-connected-clusters.md
           - hidden: monitor/autoops/cc-manage-users.md
-          - hidden: monitor/autoops/cc-collected-metrics.md
           - hidden: monitor/autoops/cc-cloud-connect-autoops-faq.md
           - hidden: monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md
       - file: monitor/stack-monitoring.md
