Reproduce asciidoc updates to logging and monitoring with sizing reco for ES instances

deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md

@@ -38,7 +38,7 @@ For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/aut
 ## Before you begin [logging-and-monitoring-limitations]
 
 * Some limitations apply when you use monitoring on ECH or ECE. To learn more, check the monitoring [restrictions and limitations](#restrictions-monitoring).
-* Enabling logs and monitoring consumes extra resources on a deployment. For production systems, we recommend sizing deployments with logs and monitoring enabled to at least 4 GB of RAM.
+* Enabling logs and monitoring consumes extra resources on a deployment. For production systems, we recommend sizing deployments with logs and monitoring enabled to at least 4 GB of RAM on each Elasticsearch instance.
 
 ## Monitoring for production use [logging-and-monitoring-production]
 
@@ -65,6 +65,11 @@ For monitoring indices, the retention period is configured in the `.monitoring-8
 
 Elastic manages the installation and configuration of the monitoring agent for you. When you enable monitoring on a deployment, you are configuring where the monitoring agent for your current deployment should send its logs and metrics.
 
+**Before you start**
+
+- Enabling logging and monitoring increases the resource consumption of the deployment. For production systems, we recommend sizing deployments with logging and monitoring enabled to at least 4 GB of RAM on each Elasticsearch instance.
+- Enabling logging and monitoring can trigger a plan change on your deployment. You can monitor the plan change progress from the deployment's **Activity** page.
+
 To enable monitoring on your deployment:
 
 1. Log into [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) (ECH) or [the Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md) (ECE).
@@ -82,10 +87,6 @@ To enable monitoring on your deployment:
     Remember to send logs and metrics for production deployments to a dedicated monitoring deployment, so that your production deployments are not impacted by the overhead of indexing and storing monitoring data. A dedicated monitoring deployment also gives you more control over the retention period for monitoring data.
     ::::
 
-::::{note}
-Enabling logs and monitoring may trigger a plan change on your deployment. You can monitor the plan change progress from the deployment’s **Activity** page.
-::::
-
 ## Access the monitoring application in {{kib}} [access-kibana-monitoring]
 
 With monitoring enabled for your deployment, you can access the [logs](//solutions/observability.md) and [stack monitoring](../monitoring-data/visualizing-monitoring-data.md) through {{kib}}.

raw-migrated-files/cloud/cloud/ec-monitoring-setup.md

@@ -14,7 +14,13 @@ You may also consider subscribing to incident notices reported on the {{ecloud}}
 
 ## Enable logs and metrics [ec_enable_logs_and_metrics]
 
-After you have created a new deployment, you should enable shipping logs and metrics to a monitoring deployment:
+After you have created a new deployment, you should enable shipping logs and metrics to a monitoring deployment.
+
+**Before you start**
+
+Enabling logs and metrics increases the resource consumption of the deployment. For production systems, we recommend sizing deployments with logs and metrics enabled to at least 4 GB of RAM on each Elasticsearch instance.
+
+To enable logs and metrics:
 
 1. Go to the [Deployments](https://cloud.elastic.co/deployments) page in {{ecloud}}.
 2. Find your deployment and go to the **Logs and Metrics** page.