diff --git a/docs/user/alerting/alerting-setup.asciidoc b/docs/user/alerting/alerting-setup.asciidoc
index 7e0880f6df41..7a67b3ee6c7e 100644
--- a/docs/user/alerting/alerting-setup.asciidoc
+++ b/docs/user/alerting/alerting-setup.asciidoc
@@ -1,6 +1,6 @@
[role="xpack"]
[[alerting-setup]]
-== Alerting Set up
+== Alerting set up
++++
Set up
++++
@@ -20,6 +20,8 @@ If you are using an *on-premises* Elastic Stack deployment with <> to secure background rule checks and actions, and API keys require {ref}/configuring-tls.html#tls-http[TLS on the HTTP interface]. A proxy will not suffice.
* If you have enabled TLS and are still unable to access Alerting, ensure that you have not {ref}/security-settings.html#api-key-service-settings[explicitly disabled API keys].
+The Alerting framework uses queries that require the `search.allow_expensive_queries` setting to be `true`. See the scripts {ref}/query-dsl-script-query.html#_allow_expensive_queries_4[documentation].
+
[float]
[[alerting-setup-production]]
=== Production considerations and scaling guidance