Could not parse input for watch . key extraction is not supported for content – Elasticsearch Error How To Solve Related Issues



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

throw new ElasticsearchParseException("could not parse [{}] input for watch [{}]. missing require [{}] field"; TYPE; watchId;
  Field.REQUEST.getPreferredName());
  }
 
  if (expectedResponseBodyType == HttpContentType.TEXT && extract != null ) {
  throw new ElasticsearchParseException("could not parse [{}] input for watch [{}]. key extraction is not supported for content" +
  " type [{}]"; TYPE; watchId; expectedResponseBodyType);
  }
 
  return new HttpInput(request; expectedResponseBodyType; extract);
  }

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 Getting JsonMappingException while sending data to view -views 71,715 ,score 20

ELK parse json field as seperate fields -views   3,209,score 2



Find Configuration Errors

Analyze Now