Could not parse action /. failed to parse field as time value – 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 action /. failed to parse field as time value ” 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 action [{}/{}]. failed to parse field [{}] as time value”classname  is ActionWrapper.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

throttlePeriod = timeValueMillis(parser.longValue());
 } else if (ThrottlerField.THROTTLE_PERIOD_HUMAN.match(currentFieldName; parser.getDeprecationHandler())) {
 try {
 throttlePeriod = WatcherDateTimeUtils.parseTimeValue(parser; ThrottlerField.THROTTLE_PERIOD_HUMAN.toString());
 } catch (ElasticsearchParseException pe) {
 throw new ElasticsearchParseException("could not parse action [{}/{}]. failed to parse field [{}] as time value";
 pe; watchId; actionId; currentFieldName);
 }
 } else if (WatchField.MAX_ITERATIONS.match(currentFieldName; parser.getDeprecationHandler())) {
 maxIterations = parser.intValue();
 } else {

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content