move page + related edits

wajihaparvez · wajihaparvez · commit 2821908d2045 · 2025-06-16T12:02:18.000-04:00
diff --git a/deploy-manage/images/stack-monitoring-dedicated-cluster-setup.png b/deploy-manage/images/stack-monitoring-dedicated-cluster-setup.png
diff --git a/deploy-manage/images/stack-monitoring-self-monitoring-cluster-setup.png b/deploy-manage/images/stack-monitoring-self-monitoring-cluster-setup.png
diff --git a/deploy-manage/monitor.md b/deploy-manage/monitor.md
@@ -23,15 +23,24 @@ Depending on your deployment type, you can use a variety of solutions for monito
 
 Depending on your deployment type and context, you have several options for monitoring your cluster or deployment.
 
+If you’re using {{ech}}, you can use [AutoOps](/deploy-manage/monitor/autoops.md) to monitor your cluster. 
+
+AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection, and resolution paths. AutoOps is [rolling out](/deploy-manage/monitor/autoops/ec-autoops-regions.md) in phases across {{ech}} regions and cloud service providers. It will be automatically activated for your deployment with no installation required.
+
+For other deployment types, use [Stack Monitoring](/deploy-manage/monitor/stack-monitoring.md) to monitor logs and metrics across the {{stack}}.
+
+To help you make your decision, refer to [AutoOps vs. Stack Monitoring](/deploy-manage/monitor/autoops-vs-stack-monitoring.md).
+
 ### AutoOps (recommended)
 
 ```{applies_to}
 deployment:
   ess:
 ```
 
-:::{include} /deploy-manage/monitor/_snippets/autoops.md
-:::
+AutoOps diagnoses issues in {{es}} by analyzing hundreds of metrics, providing root-cause analysis and accurate resolution paths. With AutoOps, customers can prevent and resolve issues, cut down administration time, and optimize resource utilization.
+
+AutoOps is currently only available for Elastic Cloud Hosted deployments.
 
 ### Stack monitoring
 
diff --git a/deploy-manage/monitor/_snippets/autoops.md b/deploy-manage/monitor/_snippets/autoops.md
@@ -1,5 +1,5 @@
-If you’re using {{ech}}, then you can use [AutoOps](/deploy-manage/monitor/autoops.md) to monitor your cluster. 
+If you’re using {{ech}}, you can use [AutoOps](/deploy-manage/monitor/autoops.md) to monitor your cluster. 
 
 AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection, and resolution paths. AutoOps is [rolling out](/deploy-manage/monitor/autoops/ec-autoops-regions.md) in phases across {{ech}} regions and cloud service providers. It will be automatically activated for your deployment with no installation required.
 
-To help you make your decision, refer to [AutoOps and Stack Monitoring comparison](/deploy-manage/monitor/autoops/autoops-stack-monitoring-comparison.md).
+To help you make your decision, refer to [](/deploy-manage/monitor/autoops-vs-stack-monitoring.md).
diff --git a/deploy-manage/monitor/autoops-vs-stack-monitoring.md b/deploy-manage/monitor/autoops-vs-stack-monitoring.md
@@ -5,10 +5,10 @@ applies_to:
     ece: all
     eck: all
     self: all
-navigation_title: AutoOps and Stack Monitoring comparison
+navigation_title: AutoOps vs. Stack Monitoring
 ---
 
-# AutoOps and Stack Monitoring comparison
+# AutoOps vs. Stack Monitoring
 
 This page provides a detailed comparison of AutoOps and Stack Monitoring to help you decide which solution is better suited to your needs.
 
@@ -26,7 +26,7 @@ With Stack Monitoring, you are responsible for storing your monitoring data. Thi
 ### Setup
 
 #### AutoOps [ao-setup]
-On {{ech}} (ECH), AutoOps is set up and enabled automatically in all [supported regions](ec-autoops-regions.md), with no action required from you.
+On {{ech}} (ECH), AutoOps is set up and enabled automatically in all supported [regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md), with no action required from you.
 
 :::{note}
 AutoOps is planned to be available in self-managed environments in the future.
@@ -58,17 +58,17 @@ You can store your Stack Monitoring logs and metrics in the following ways:
 ### Availability
 
 #### AutoOps [ao-availability]
-AutoOps lives in {{ecloud}}, so you need to have an {{ecloud}} account to access it. Once logged in, you can [access](ec-autoops-how-to-access.md) AutoOps from your hosted deployments.
+AutoOps lives in {{ecloud}}, so you need to have an {{ecloud}} account to access it. Once logged in, you can [access](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md) AutoOps from your hosted deployments.
 
 #### Stack Monitoring [sm-availability]
 Once setup is complete, you can access the Stack Monitoring UI inside {{kib}}, where you can monitor all your {{stack}} components.
 
 ### Investigations and root cause analysis
 
 #### AutoOps [ao-investigations]
-The AutoOps agent captures a pre-defined set of {{es}} metrics, but doesn’t fetch any logs. AutoOps then performs multi-metrics analysis and correlations to identify issues and potential root causes. When issues are detected, AutoOps raises [events](ec-autoops-events.md) and [notifies](ec-autoops-notifications-settings.md) you accordingly. When the issue is resolved, AutoOps automatically closes the event.
+The AutoOps agent captures a pre-defined set of {{es}} metrics, but doesn’t fetch any logs. AutoOps then performs multi-metrics analysis and correlations to identify issues and potential root causes. When issues are detected, AutoOps raises [events](/deploy-manage/monitor/autoops/ec-autoops-events.md) and [notifies](/deploy-manage/monitor/autoops/ec-autoops-notifications-settings.md) you accordingly. When the issue is resolved, AutoOps automatically closes the event.
 
-For each raised event, AutoOps provides insights into the affected resources (cluster, node, index, shard, etc.), background information on the detected problem, and step-by-step guides to help you diagnose and remediate the identified issues. Most detection rules can be [customized](ec-autoops-event-settings.md) by adjusting thresholds, durations, index patterns, data tiers, and more.
+For each raised event, AutoOps provides insights into the affected resources (cluster, node, index, shard, etc.), background information on the detected problem, and step-by-step guides to help you diagnose and remediate the identified issues. Most detection rules can be [customized](/deploy-manage/monitor/autoops/ec-autoops-event-settings.md) by adjusting thresholds, durations, index patterns, data tiers, and more.
 
 #### Stack Monitoring [sm-investigations]
 The Stack Monitoring UI displays the [metrics](/deploy-manage/monitor/monitoring-data/elasticsearch-metrics.md) of your monitored {{stack}} components over time. Logs can be viewed, searched, and filtered in Discover. You can enable a pre-defined set of alerts that are triggered when specific thresholds are crossed. You can also configure your own [alerts](/deploy-manage/monitor/monitoring-data/configure-stack-monitoring-alerts.md) on any collected metrics or log messages. However, Stack Monitoring does not offer any further investigation, correlations, or root cause analyses.
diff --git a/deploy-manage/monitor/autoops/ec-autoops-faq.md b/deploy-manage/monitor/autoops/ec-autoops-faq.md
@@ -40,5 +40,5 @@ $$$faq-autoops-metrics-storage$$$Where are AutoOps metrics stored, and does Auto
 :   AutoOps metrics are stored internally within the Elastic infrastructure, not on customer deployments. So using AutoOps does not consume customer ECU.
 
 $$$faq-autoops-vs-stack-monitoring$$$Has AutoOps replaced Stack Monitoring?
-:   Currently, AutoOps has many of the same features as Stack Monitoring as well as several new ones. However, it only provides insights on {{es}} and analyzes metrics, but not logs. Read more in [AutoOps and Stack Monitoring comparison](/deploy-manage/monitor/autoops/autoops-stack-monitoring-comparison.md).
+:   Currently, AutoOps has many of the same features as Stack Monitoring as well as several new ones. However, it only provides insights on {{es}} and analyzes metrics, but not logs. Read more in [](/deploy-manage/monitor/autoops-vs-stack-monitoring.md).
 
diff --git a/deploy-manage/toc.yml b/deploy-manage/toc.yml
@@ -662,7 +662,6 @@ toc:
           - file: monitor/autoops/ec-autoops-dismiss-event.md
           - file: monitor/autoops/ec-autoops-regions.md
           - file: monitor/autoops/ec-autoops-faq.md
-          - file: monitor/autoops/autoops-stack-monitoring-comparison.md
       - file: monitor/stack-monitoring.md
         children:
           - file: monitor/stack-monitoring/ece-ech-stack-monitoring.md
@@ -699,6 +698,7 @@ toc:
               - file: monitor/monitoring-data/config-monitoring-data-streams-elastic-agent.md
               - file: monitor/monitoring-data/config-monitoring-data-streams-metricbeat-8.md
               - file: monitor/monitoring-data/config-monitoring-indices-metricbeat-7-internal-collection.md
+      - file: monitor/autoops-vs-stack-monitoring.md
       - file: monitor/cloud-health-perf.md
         children:
           - file: monitor/access-performance-metrics-on-elastic-cloud.md
