[8.5] [Known Issue] Add docs to describe a known issue/limitation of …

…EQL rule cross-cluster search (#4813) (#4926)

* [Known Issue] Add docs to describe a known issue/limitation of EQL rule cross-cluster search (#4813)

# Conflicts:
#	docs/detections/api/rules/rules-api-create.asciidoc
#	docs/detections/rules-ui-create.asciidoc

* Removed merge markers

* Update docs/detections/api/rules/rules-api-create.asciidoc

* Update docs/detections/rules-ui-create.asciidoc

docs/detections/api/rules/rules-api-create.asciidoc

@@ -399,11 +399,16 @@ documents from the {es} index containing the threat values.
 context] array used to define the conditions for when alerts are created from
 events. Defaults to an empty array.
 
-|index |String[] |Indices on which the rule functions. Defaults to the
+|index |String[] a|Indices on which the rule functions. Defaults to the
 Security Solution indices defined on the {kib} Advanced Settings page
 (*Kibana* → *Stack Management* → *Advanced Settings* →
 `securitySolution:defaultIndex`).
 
+[NOTE]
+======
+Event correlation rules have a limitation that prevents them from querying multiple indices from different clusters (local and remote). To enable this, a user with the {ref}/built-in-roles.html[`superuser`] role must modify the EQL rules that are configured to use <<sec-requirements,cross-cluster search>>. This updates the rule's API key to use `superuser` privileges and allows the rule to use cross-cluster search.
+======
+
 |risk_score_mapping |Object[] a|Overrides generated alerts' `risk_score` with
 a value from the source event:
 

docs/detections/rules-ui-create.asciidoc

@@ -190,6 +190,8 @@ IMPORTANT: Alerts created by threshold rules are synthetic alerts that do not re
 ==== Create an event correlation rule
 . To create an event correlation rule using EQL, select *Event Correlation*, then:
 .. Define which {es} indices or data view the rule searches for alerts.
++
+NOTE: Event correlation rules have a limitation that prevents them from querying multiple indices from different clusters (local and remote). To enable this, a user with the {ref}/built-in-roles.html[`superuser`] role must modify the EQL rules that are configured to use <<sec-requirements,cross-cluster search>>. This updates the rule's API key to use `superuser` privileges and allows the rule to use cross-cluster search.
 .. Add an {ref}/eql-syntax.html[EQL statement] used to detect alerts.
 +
 For example, the following rule detects when `msxsl.exe` makes an outbound