Adding elasticsearch.requestHeaders option to kibana.yml and documentation

This commit is contained in:
Shaunak Kashyap 2016-04-13 16:56:26 -07:00
parent b102e26ac3
commit b635b2c466
No known key found for this signature in database
GPG key ID: 0512E188DDE4FF2A
3 changed files with 9 additions and 1 deletions

View file

@ -61,6 +61,9 @@
# must be a positive integer.
# elasticsearch.requestTimeout: 30000
# List of Kibana client-side headers to send to Elasticsearch
# elasticsearch.requestHeaders: [ ]
# Time in milliseconds for Elasticsearch to wait for responses from shards. Set to 0 to disable.
# elasticsearch.shardTimeout: 0

View file

@ -29,7 +29,8 @@ to `false`.
wait for Elasticsearch to respond to pings.
`elasticsearch.requestTimeout:`:: *Default: 300000* Time in milliseconds to wait for responses from the back end or
Elasticsearch. This value must be a positive integer.
`elasticsearch.shardTimeout:`:: *Default: 0* Time in milliseconds for Elasticsearch to wait for responses from shards. Set
`elasticsearch.requestHeaders:`:: *Default: `[]`* List of Kibana client-side headers to send to Elasticsearch.
`elasticsearch.shardTimeout:`:: *Default: 0* Time in milliseconds for Elasticsearch to wait for responses from shards. Set
to 0 to disable.
`elasticsearch.startupTimeout:`:: *Default: 5000* Time in milliseconds to wait for Elasticsearch at Kibana startup before
retrying.

View file

@ -376,6 +376,10 @@ deprecated[4.2, The names of several Kibana server properties changed in the 4.2
+
*default*: `500000`
`elasticsearch.requestHeaders:` added[5.0]:: List of Kibana client-side headers to send to Elasticsearch.
+
*default*: `[]`
`elasticsearch.shardTimeout` added[4.2]:: How long Elasticsearch should wait for responses from shards. Set to 0 to disable.
+
*alias*: `shard_timeout` deprecated[4.2]