Deprecate internal legacy monitoring and flag for removal in v10.

deploy-manage/monitor/stack-monitoring/_snippets/legacy-warning.md

@@ -1,5 +1,8 @@
-:::{important}
-{{agent}} and {{metricbeat}} are the recommended methods for collecting and shipping monitoring data to a monitoring cluster.
+:::{warning}
+The {{es}} Monitoring plugin is deprecated and will be removed in 10.0. Choose one of the following replacements to monitor your {{es}} cluster:
 
-If you have previously configured legacy collection methods, you should migrate to using [{{agent}}](/deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-elastic-agent.md) or [{{metricbeat}}](/deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-metricbeat.md) collection. Do not use legacy collection alongside other collection methods.
+* **[AutoOps](/deploy-manage/monitor/autoops.md)** (recommended): Simplifies cluster management through performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths.
+* **Stack monitoring with [{{agent}}](/deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-elastic-agent.md) or [{{metricbeat}}](/deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-metricbeat.md)**: Collect logs and metrics from {{es}} and ship them to a monitoring cluster for visualization in {{kib}}.
+
+To help you decide, refer to the [AutoOps and Stack Monitoring comparison](/deploy-manage/monitor/autoops-vs-stack-monitoring.md).
 :::

deploy-manage/monitor/stack-monitoring/es-http-exporter.md

@@ -3,19 +3,21 @@ mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/http-exporter.html
 applies_to:
   deployment:
-    self: deprecated 7.16.0
+    self: deprecated 7.16, removed 10.0
 products:
   - id: elasticsearch
 ---
 
 
 # HTTP exporters [http-exporter]
 
-::::{important}
-{{agent}} and {{metricbeat}} are the recommended methods for collecting and shipping monitoring data to a monitoring cluster.
+::::{warning}
+The {{es}} Monitoring plugin is deprecated and will be removed in 10.0. Choose one of the following replacements to monitor your {{es}} cluster:
 
-If you have previously configured legacy collection methods, you should migrate to using [{{agent}}](collecting-monitoring-data-with-elastic-agent.md) or [{{metricbeat}}](collecting-monitoring-data-with-metricbeat.md) collection. Do not use legacy collection alongside other collection methods.
+* **[AutoOps](../autoops.md)** (recommended): Simplifies cluster management through performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths.
+* **Stack monitoring with [{{agent}}](collecting-monitoring-data-with-elastic-agent.md) or [{{metricbeat}}](collecting-monitoring-data-with-metricbeat.md)**: Collect logs and metrics from {{es}} and ship them to a monitoring cluster for visualization in {{kib}}.
 
+To help you decide, refer to the [AutoOps and Stack Monitoring comparison](../autoops-vs-stack-monitoring.md).
 ::::
 
 

deploy-manage/monitor/stack-monitoring/es-legacy-collection-methods.md

@@ -4,16 +4,21 @@ mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/collecting-monitoring-data.html
 applies_to:
   deployment:
-    self: deprecated 7.16.0
+    self: deprecated 7.16, removed 10.0
 products:
   - id: elasticsearch
 ---
 
 # Legacy collection methods for self-managed {{es}} [collecting-monitoring-data]
 
 
-::::{admonition} Deprecated in 7.16
-Using the {{es}} Monitoring plugin to collect and ship monitoring data is deprecated. {{agent}} and {{metricbeat}} are the recommended methods for collecting and shipping monitoring data to a monitoring cluster. If you previously configured legacy collection methods, you should migrate to using [{{agent}}](collecting-monitoring-data-with-elastic-agent.md) or [{{metricbeat}}](collecting-monitoring-data-with-metricbeat.md) collection methods.
+::::{warning}
+The {{es}} Monitoring plugin is deprecated and will be removed in 10.0. Choose one of the following replacements to monitor your {{es}} cluster:
+
+* **[AutoOps](../autoops.md)** (recommended): Simplifies cluster management through performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths.
+* **Stack monitoring with [{{agent}}](collecting-monitoring-data-with-elastic-agent.md) or [{{metricbeat}}](collecting-monitoring-data-with-metricbeat.md)**: Collect logs and metrics from {{es}} and ship them to a monitoring cluster for visualization in {{kib}}.
+
+To help you decide, refer to the [AutoOps and Stack Monitoring comparison](../autoops-vs-stack-monitoring.md).
 ::::
 
 

deploy-manage/monitor/stack-monitoring/es-local-exporter.md

@@ -3,7 +3,7 @@ mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/local-exporter.html
 applies_to:
   deployment:
-    self: deprecated 7.16.0
+    self: deprecated 7.16, removed 10.0
 products:
   - id: elasticsearch
 ---

deploy-manage/monitor/stack-monitoring/es-monitoring-collectors.md

@@ -3,7 +3,7 @@ mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/es-monitoring-collectors.html
 applies_to:
   deployment:
-    self: deprecated 7.16.0
+    self: deprecated 7.16, removed 10.0
 products:
   - id: elasticsearch
 ---

deploy-manage/monitor/stack-monitoring/es-monitoring-exporters.md

@@ -3,7 +3,7 @@ mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/es-monitoring-exporters.html
 applies_to:
   deployment:
-    self: deprecated 7.16.0
+    self: deprecated 7.16, removed 10.0
 products:
   - id: elasticsearch
 ---

deploy-manage/monitor/stack-monitoring/es-pause-export.md

@@ -3,7 +3,7 @@ mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/pause-export.html
 applies_to:
   deployment:
-    self: deprecated 7.16.0
+    self: deprecated 7.16, removed 10.0
 products:
   - id: elasticsearch
 ---

deploy-manage/monitor/stack-monitoring/kibana-monitoring-legacy.md

@@ -4,7 +4,7 @@ mapped_pages:
   - https://www.elastic.co/guide/en/kibana/current/monitoring-kibana.html
 applies_to:
   deployment:
-    self: deprecated 7.16.0
+    self: deprecated 7.16, removed 10.0
 products:
   - id: kibana
 ---
@@ -17,13 +17,13 @@ products:
 
 If you enable the Elastic {{monitor-features}} in your cluster, you can optionally collect metrics about {{kib}}.
 
-::::{important}
-{{agent}} and {{metricbeat}} are the recommended methods for collecting and shipping monitoring data to a monitoring cluster.
+::::{warning}
+The {{es}} Monitoring plugin is deprecated and will be removed in 10.0. Choose one of the following replacements to monitor your {{kib}} instance:
 
-If you have previously configured legacy collection methods, you should migrate to using {{agent}} or {{metricbeat}} collection. Do not use legacy collection alongside other collection methods.
-
-For more information, refer to [](kibana-monitoring-elastic-agent.md) and [](kibana-monitoring-metricbeat.md).
+* **[AutoOps](../autoops.md)** (recommended): Simplifies cluster management through performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths.
+* **Stack monitoring with [{{agent}}](kibana-monitoring-elastic-agent.md) or [{{metricbeat}}](kibana-monitoring-metricbeat.md)**: Collect logs and metrics from {{kib}} and ship them to a monitoring cluster for visualization in {{kib}}.
 
+To help you decide, refer to the [AutoOps and Stack Monitoring comparison](../autoops-vs-stack-monitoring.md).
 ::::