Could not parse time – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch is unable to parse the time format provided. This could be due to an incorrect or unsupported time format. To resolve this issue, ensure that the time format is in a format that Elasticsearch can understand, such as ISO 8601. Alternatively, you can use the “date” filter in Logstash to specify the correct format. If you’re using a custom time format, make sure it’s correctly implemented and matches the actual data.

This guide will help you check for common problems that cause the log ” could not parse time [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “could not parse time [{}]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 throw new ElasticsearchParseException("could not parse time [{}]. time minute [{}] is not a number"; time; minStr);
 try {
 return new DayTimes(time; hour; minute);
 } catch (IllegalArgumentException iae) {
 throw new ElasticsearchParseException("could not parse time [{}]"; iae);
 }  public void validate() {
 for (int i = 0; i < hour.length; i++) {


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?