Allow configuration of the default index pattern creation string

[ggrossetie]

The default behavior has unwanted effects because the query used to fetch field mappings consumes a lot of ressources. We even experienced nodes failures during the initialization of Kibana.

As a workaround we've initialized Kibana index with curl queries but if someone inadvertently click on "Settings > Indices" tab, the query will run automatically once again 😞

I think the default value should be blank.

Another solution is to require an action from the user to effectively fetch mapping (click on a button).

[rashidkpc]

I somewhat agree here, but this sounds like an Elasticsearch bug. If Elasticsearch is crashing when making a call to _mappings, that seems like a big problem. Can you file an issue on elastic/elasticsearch?

[ggrossetie]

Hello @rashidkpc

I somewhat agree here

Thanks 😄
I'm not familiar with the Kibana code but I will try to provide a pull request. Any preferences on the approach (ie. click on the button or blank field) ?

but this sounds like an Elasticsearch bug. If Elasticsearch is crashing when making a call to _mappings, that seems like a big problem. Can you file an issue on elastic/elasticsearch?

I think the problem is well known on Elasticsearch, and related to the fact that mappings are associated on types. See elastic/elasticsearch#15728

On my cluster the response size of http://localhost:9200/_cluster/state/ is about 15 Mo... I don't know exactly what queries are executed by Kibana but I think _cluster/state/ is one of them.
I will try to debug further to find the root cause.

[ggrossetie]

I will try to debug further to find the root cause.

@rashidkpc I think I found the root cause: elastic/elasticsearch#15789

[epixa]

Given that the corresponding bug in elasticsearch was fixed, is this necessary anymore?

[ggrossetie]

Indeed elastic/elasticsearch#15789 was fixed but this enhancement remains useful for users that don't want to work on "logstash-*" indices.