Could not parse date/time. expected date field to be either a number or a – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” could not parse date/time. expected date field to be either a number or a ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “could not parse date/time. expected date field [{}] to be either a number or a”classname  is WatcherDateTimeUtils.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

}
 if (token == XContentParser.Token.VALUE_STRING) {
 try {
 return parseDateMath(parser.text(); timeZone; clock);
 } catch (ElasticsearchParseException epe) {
 throw new ElasticsearchParseException("could not parse date/time. expected date field [{}] to be either a number or a " +
 "DateMath string but found [{}] instead"; epe; fieldName; parser.text());
 }
 }
 if (token == XContentParser.Token.VALUE_NULL) {
 return null;

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content