[DOCS] Adds monitoring requirement for ingest node (#36665)

Author: lcawl

docs/reference/monitoring/configuring-monitoring.asciidoc

@@ -6,10 +6,14 @@
 <titleabbrev>Configuring monitoring</titleabbrev>
 ++++
 
-By default, {monitoring} is enabled but data collection is disabled. Advanced
-monitoring settings enable you to control how frequently data is collected,
-configure timeouts, and set the retention period for locally-stored monitoring
-indices. You can also adjust how monitoring data is displayed. 
+
+If you enable the Elastic {monitor-features} in your cluster, you can optionally
+collect metrics about {es}. By default, monitoring is enabled but data
+collection is disabled. 
+
+Advanced monitoring settings enable you to control how frequently data is
+collected, configure timeouts, and set the retention period for locally-stored
+monitoring indices. You can also adjust how monitoring data is displayed. 
 
 . To collect monitoring data about your {es} cluster:
 
@@ -47,27 +51,33 @@ as {kib}, Beats, and Logstash to a monitoring cluster:
 .. Verify that `xpack.monitoring.collection.enabled` settings are `true` on each 
 node in the cluster. 
 
-..  {stack-ov}/xpack-monitoring.html[Configure {monitoring} across the Elastic Stack].
+..  {stack-ov}/xpack-monitoring.html[Configure monitoring across the {stack}].
 
 . Identify where to store monitoring data. 
 +
 --
-By default, {monitoring} uses a `local` exporter that indexes monitoring data 
-on the same cluster. See <<es-monitoring-default-exporter>> and <<local-exporter>>. 
+By default, {es} {monitor-features} use a `local` exporter that indexes
+monitoring data on the same cluster. See <<es-monitoring-default-exporter>> and
+<<local-exporter>>. 
 
 Alternatively, you can use an `http` exporter to send data to a separate 
 monitoring cluster. See <<http-exporter>>. 
 
+IMPORTANT: The {es} {monitor-features} use ingest pipelines, therefore the
+cluster that stores the monitoring data must have at least one 
+<<ingest,ingest node>>.
+
 For more information about typical monitoring architectures, 
 see {stack-ov}/how-monitoring-works.html[How Monitoring Works].
 --
 
-. If {security} is enabled and you are using an `http` exporter to send data to 
- a dedicated monitoring cluster: 
+. If {es} {security-features} are enabled and you are using an `http` exporter
+to send data to a dedicated monitoring cluster: 
 
 .. Create a user on the monitoring cluster that has the 
-{xpack-ref}/built-in-roles.html#built-in-roles-remote-monitoring-agent[`remote_monitoring_agent` built-in role]. For example, the following request
-creates a `remote_monitor` user that has the `remote_monitoring_agent` role:
+{stack-ov}/built-in-roles.html#built-in-roles-remote-monitoring-agent[`remote_monitoring_agent` built-in role].
+For example, the following request creates a `remote_monitor` user that has the
+`remote_monitoring_agent` role:
 +
 --
 [source, sh]
@@ -84,12 +94,17 @@ POST /_xpack/security/user/remote_monitor
 --
 
 .. On each node in the cluster that is being monitored, configure the `http` 
-exporter to use the appropriate credentials when data is shipped to the monitoring cluster. 
+exporter to use the appropriate credentials when data is shipped to the
+monitoring cluster. 
 +
 --
-If SSL/TLS is enabled on the monitoring cluster, you must use the HTTPS protocol in the `host` setting. You must also include the CA certificate in each node's trusted certificates in order to verify the identities of the nodes in the monitoring cluster. 
+If SSL/TLS is enabled on the monitoring cluster, you must use the HTTPS protocol
+in the `host` setting. You must also include the CA certificate in each node's
+trusted certificates in order to verify the identities of the nodes in the
+monitoring cluster. 
 
-The following example specifies the location of the PEM encoded certificate with the `certificate_authorities` setting:
+The following example specifies the location of the PEM encoded certificate with
+the `certificate_authorities` setting:
 
 [source,yaml]
 --------------------------------------------------
@@ -127,14 +142,15 @@ xpack.monitoring.exporters:
 --------------------------------------------------
 --
 
-. If {security} is enabled and you want to visualize monitoring data in {kib}, 
-you must create users that have access to the {kib} indices and permission to 
-read from the monitoring indices.
+. If the {es} {security-features} are enabled and you want to visualize
+monitoring data in {kib}, you must create users that have access to the {kib}
+indices and permission to read from the monitoring indices.
 +
 --
-You set up {monitoring} UI users on the cluster where the monitoring data is 
-stored, that is to say the monitoring cluster. To grant all of the necessary permissions, assign users the
-`monitoring_user` and `kibana_user` roles. For more information, see 
+You set up Monitoring UI users on the cluster where the monitoring data is 
+stored, that is to say the monitoring cluster. To grant all of the necessary
+permissions, assign users the `monitoring_user` and `kibana_user` roles. For
+more information, see 
 {stack-ov}/mapping-roles.html[Mapping users and groups to roles].
 --