Could not parse watch status. expecting field to be an object; – How to solve this Elasticsearch error

Average Read Time

2 Mins

Could not parse watch status. expecting field to be an object; – 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 watch status. expecting field to be an object; ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: rest-high-level and client.

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 watch status. expecting field [{}] to be an object;”classname  is WatchStatus.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

ActionStatus actionStatus = ActionStatus.parse(currentFieldName; parser);
 actions.put(currentFieldName; actionStatus);
 }
 }
 } else {
 throw new ElasticsearchParseException("could not parse watch status. expecting field [{}] to be an object; " +
 "found [{}] instead"; currentFieldName; token);
 }
 } else if (Field.HEADERS.match(currentFieldName; parser.getDeprecationHandler())) {
 if (token == XContentParser.Token.START_OBJECT) {
 headers = parser.mapStrings();

 

Watch a demo of the Check-Up:

Analyze your cluster

Skip to content