please see the follow: [image] why es parse log level as a int value? if i change the log level to int value and this problem is resolved,but not my need.

Hi,i meet a problem in es

lmx1989219 (lucas) March 4, 2016, 9:57am 4

i use heka collect json log data to es directly.
and i do not specified the es dynamic mappings the up you said.

Topic		Replies	Views
ElasticSearch saving integer field as String Elasticsearch	3	2012	July 6, 2017
ES attempting to parse dates automatically (possibly Hadoop related) Elasticsearch	12	1239	July 6, 2017
Org.elasticsearch.index.mapper.MapperParsingException: failed to parse - need guidance Elasticsearch	2	1559	July 6, 2017
Mapper_parsing_exception", "reason"=>"failed to parse [severity]" Logstash	10	28626	May 21, 2018
Mapper parsing exception - failed to parse field Logstash	10	8712	May 8, 2022