update docs (#47791)

(cherry picked from commit 56a35a9)

Author: VihasMakwana

docs/reference/auditbeat/elasticsearch-output.md

@@ -81,6 +81,10 @@ The list of Elasticsearch nodes to connect to. The events are distributed to the
 When a node is defined as an `IP:PORT`, the *scheme* and *path* are taken from the [`protocol`](#protocol-option) and [`path`](#path-option) config options.
 ::::
 
+::::{warning}
+All configured hosts must belong to the same Elasticsearch cluster; using nodes from different clusters may result in split or inconsistent data.
+::::
+
 
 ```yaml
 output.elasticsearch:

docs/reference/filebeat/elasticsearch-output.md

@@ -81,6 +81,10 @@ The list of Elasticsearch nodes to connect to. The events are distributed to the
 When a node is defined as an `IP:PORT`, the *scheme* and *path* are taken from the [`protocol`](#protocol-option) and [`path`](#path-option) config options.
 ::::
 
+::::{warning}
+All configured hosts must belong to the same Elasticsearch cluster; using nodes from different clusters may result in split or inconsistent data.
+::::
+
 
 ```yaml
 output.elasticsearch:

docs/reference/heartbeat/elasticsearch-output.md

@@ -81,6 +81,10 @@ The list of Elasticsearch nodes to connect to. The events are distributed to the
 When a node is defined as an `IP:PORT`, the *scheme* and *path* are taken from the [`protocol`](#protocol-option) and [`path`](#path-option) config options.
 ::::
 
+::::{warning}
+All configured hosts must belong to the same Elasticsearch cluster; using nodes from different clusters may result in split or inconsistent data.
+::::
+
 
 ```yaml
 output.elasticsearch:

docs/reference/metricbeat/elasticsearch-output.md

@@ -81,6 +81,10 @@ The list of Elasticsearch nodes to connect to. The events are distributed to the
 When a node is defined as an `IP:PORT`, the *scheme* and *path* are taken from the [`protocol`](#protocol-option) and [`path`](#path-option) config options.
 ::::
 
+::::{warning}
+All configured hosts must belong to the same Elasticsearch cluster; using nodes from different clusters may result in split or inconsistent data.
+::::
+
 
 ```yaml
 output.elasticsearch:

docs/reference/packetbeat/elasticsearch-output.md

@@ -81,6 +81,10 @@ The list of Elasticsearch nodes to connect to. The events are distributed to the
 When a node is defined as an `IP:PORT`, the *scheme* and *path* are taken from the [`protocol`](#protocol-option) and [`path`](#path-option) config options.
 ::::
 
+::::{warning}
+All configured hosts must belong to the same Elasticsearch cluster; using nodes from different clusters may result in split or inconsistent data.
+::::
+
 
 ```yaml
 output.elasticsearch:

docs/reference/winlogbeat/elasticsearch-output.md

@@ -81,6 +81,10 @@ The list of Elasticsearch nodes to connect to. The events are distributed to the
 When a node is defined as an `IP:PORT`, the *scheme* and *path* are taken from the [`protocol`](#protocol-option) and [`path`](#path-option) config options.
 ::::
 
+::::{warning}
+All configured hosts must belong to the same Elasticsearch cluster; using nodes from different clusters may result in split or inconsistent data.
+::::
+
 
 ```yaml
 output.elasticsearch: