maxmustermann/kibana
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

[Alerting][Docs] Elasticsearch setting search.allow_expensive_queries should be set as true. (#113062) (#113863)

Browse source 
* [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:
Yuliia Naumenko 2021-10-04 15:29:30 -07:00 committed by GitHub
parent 6be9fbe9c7
commit 2fec59867a
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/user/alerting/alerting-setup.asciidoc
View file

@ -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 {ref}/security-basic-setup-https.html#encrypt-kibana-elasticsearch[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