I've taken on an environment and am getting up to speed on the ELK stack. In some of my old indices are a lot of randomly named fields where a URI or some HTTP content has been passed in and not correctly parsed into fields. I've created a new EL2.1 cluster and would like to prevent this in future.…

Using "dynamic" : "strict" to prevent unintended fields from being created?

jpountz (Adrien Grand) November 30, 2015, 5:37pm 2

Maybe dynamic: false is what you are looking for? It will ignore all fields that are not defined in the mappings (but they will still remain accessible via the _source).

Topic		Replies	Views
Allowing only fields described in dynamic templates Elasticsearch	3	593	July 5, 2017
Strict dynamic mapping and dynamic template matches Elasticsearch	2	803	July 6, 2017
Dynamic mapping setting not honoured Elasticsearch	2	490	February 28, 2021
Only speficied fields Elasticsearch	14	7898	June 21, 2017
Dynamic mapping strict to true Elasticsearch	11	12031	May 12, 2021

Using "dynamic" : "strict" to prevent unintended fields from being created?

Related topics