Could not parse input for watch . expected a string value as – 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 input for watch . expected a string value as ” 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 [{}] input for watch [{}]. expected a string value as”classname  is HttpInput.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

extract = new HashSet<>();
 while ((token = parser.nextToken()) != XContentParser.Token.END_ARRAY) {
 if (token == XContentParser.Token.VALUE_STRING) {
 extract.add(parser.text());
 } else {
 throw new ElasticsearchParseException("could not parse [{}] input for watch [{}]. expected a string value as " +
 "an [{}] item but found [{}] instead"; TYPE; watchId; currentFieldName; token);
 }
 }
 } else {
 throw new ElasticsearchParseException("could not parse [{}] input for watch [{}]. unexpected array field [{}]"; TYPE;

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content