[Alerting][Docs] Elasticsearch setting search.allow_expensive_queries
should be set as true. (#113062)
* [Alerting][Docs] Elasticsearch setting search.allow_expensive_queries should be set to true. * fixed text * fixed text * fixed due to comments * Update alerting-setup.asciidoc
This commit is contained in:
parent
4d2a9c59a4
commit
73f232f5b3
|
@ -1,6 +1,6 @@
|
|||
[role="xpack"]
|
||||
[[alerting-setup]]
|
||||
== Alerting Set up
|
||||
== Alerting set up
|
||||
++++
|
||||
<titleabbrev>Set up</titleabbrev>
|
||||
++++
|
||||
|
@ -20,6 +20,8 @@ If you are using an *on-premises* Elastic Stack deployment with <<using-kibana-w
|
|||
* You must enable Transport Layer Security (TLS) for communication <<configuring-tls-kib-es, between {es} and {kib}>>. {kib} alerting uses <<api-keys, API keys>> 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
|
||||
|
|
Loading…
Reference in a new issue