Could not parse input for watch . failed to parse – 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 Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

Briefly, this error occurs when Elasticsearch is unable to parse a watch input, which is used to define alerts and notifications based on specific conditions or events. This may be caused by a syntax error or invalid value in the input. To resolve the issue, you can try reviewing the watch input and correcting any syntax errors or invalid values, or modifying the watch input to conform to the expected syntax and structure.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

Take a self-guided product tour to see for yourself (no registration required).

This guide will help you check for common problems that cause the log ” could not parse input for watch . failed to parse ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: search and plugin.

Log Context

Log “could not parse [{}] input for watch [{}]. failed to parse [{}]”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

currentFieldName = parser.currentName();
 } else if (Field.REQUEST.match(currentFieldName; parser.getDeprecationHandler())) {
 try {
 request = WatcherSearchTemplateRequest.fromXContent(parser; ExecutableSearchInput.DEFAULT_SEARCH_TYPE);
 } catch (ElasticsearchParseException srpe) {
 throw new ElasticsearchParseException("could not parse [{}] input for watch [{}]. failed to parse [{}]"; srpe; TYPE;
 watchId; currentFieldName);
 } else if (token == XContentParser.Token.START_ARRAY) {
 if (Field.EXTRACT.match(currentFieldName; parser.getDeprecationHandler())) {
 extract = new HashSet<>();


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content