Could not parse date/time expected date field to not be null but was null – How to solve this Elasticsearch error

Could not parse date/time expected date field to not be null but was null – 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 Error 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 not be null but was null ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

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

return dateTimeFormatter.format(date);
  }
 
  public static ZonedDateTime parseDateMath(String fieldName; XContentParser parser; ZoneId timeZone; Clock clock) throws IOException {
  if (parser.currentToken() == XContentParser.Token.VALUE_NULL) {
  throw new ElasticsearchParseException("could not parse date/time expected date field [{}] to not be null but was null";
  fieldName);
  }
  return parseDateMathOrNull(fieldName; parser; timeZone; clock);
  }

 

Run the Check-Up to get a customized report like this:

Analyze your cluster