Could not parse input for watch . expected field indicating the input type; but – Elasticsearch Error How To Solve Related Issues



Could not parse input for watch . expected field indicating the input type; but – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up  which can resolve issues causing many errors 

 

This guide will help you check for common problems that cause the log “could not parse input for watch . expected field indicating the input type; but” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: plugin.


Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation). 

Log Context

Log”could not parse input for watch [{}]. expected field indicating the input type; but”classname  is InputRegistry.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

"but found [{}] instead"; watchId; type; token);
  }
  }
 
  if (input == null) {
  throw new ElasticsearchParseException("could not parse input for watch [{}]. expected field indicating the input type; but " +
  "found an empty object instead"; watchId; token);
  }
 
  return input;
  }

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 json: cannot unmarshal object into Go value of type -views 89,602 ,score 22

Watcher input extract fields – Elasticsearch – Discuss the Elastic Stack  



Find Configuration Errors

Analyze Now