Could not parse trigger event for for watch . expected trigger type string – Elasticsearch Error How To Solve Related Issues

Could not parse trigger event for for watch . expected trigger type string – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch Version: 1.7-8.0

This guide will help you check for common problems that cause the error message”could not parse trigger event for for watch . expected trigger type string”. To understand what might cause it to appear, read bellow frequent issues related to the Elasticsearch concepts: plugin.

Advanced users might want to skip right to trying out the Elasticsearch Error Check-Up, which analyses ES to discover the cause of many errors to provide actionable recommendations (JSON based, no fee and just 2 minutes to complete).

Log Context

Log”could not parse trigger event for [{}] for watch [{}]. expected trigger type string”classname  is TriggerService.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

public TriggerEvent parseTriggerEvent(String watchId; String context; XContentParser parser) throws IOException {
  XContentParser.Token token = parser.currentToken();
  assert token == XContentParser.Token.START_OBJECT;
  token = parser.nextToken();
  if (token != XContentParser.Token.FIELD_NAME) {
  throw new ElasticsearchParseException("could not parse trigger event for [{}] for watch [{}]. expected trigger type string " +
  "field; but found [{}]"; context; watchId; token);
  }
  String type = parser.currentName();
  token = parser.nextToken();
  if (token != XContentParser.Token.START_OBJECT) {

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 uncaught syntaxerror unexpected token U JSON -views 355,482 ,score 295

SyntaxError: Unexpected token o in JSON at position 1 -views   325,673,score 125

 

 

About Opster

Opster detects, prevents, optimizes and automates everything needed to run mission-critical Elasticsearch

Find Configuration Errors

Analyze Now