Could not parse condition for watch . compared value for with – 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 condition for watch . compared value for with ” 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 [{}] condition for watch [{}]. compared value for [{}] with”classname  is CompareCondition.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

throw new ElasticsearchParseException("could not parse [{}] condition for watch [{}]. unknown comparison operator " +
 "[{}]"; TYPE; watchId; parser.currentName());
 }
 token = parser.nextToken();
 if (!op.supportsStructures() && !token.isValue() && token != XContentParser.Token.VALUE_NULL) {
 throw new ElasticsearchParseException("could not parse [{}] condition for watch [{}]. compared value for [{}] with " +
 "operation [{}] must either be a numeric; string; boolean or null value; but found [{}] instead"; TYPE;
 watchId; path; op.name().toLowerCase(Locale.ROOT); token);
 }
 value = XContentUtils.readValue(parser; token);
 token = parser.nextToken();

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content