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?

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

Elasticsearch is a trademark of Elasticsearch BV, registered in the U.S. and in other countries
Trademarks
Terms
Privacy
Brand
Code of Conduct

Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.

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

Related topics