Could not parse input for watch . key extraction is not supported for content – How to solve this Elasticsearch error

Could not parse input for watch . key extraction is not supported for content – 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 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 . 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 pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (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);
  }

 

Run the Check-Up to get a customized report like this:

Analyze your cluster