Could not parse trigger event for 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 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 trigger event for for watch . failed to parse ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

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

} else if (Field.TRIGGERED_TIME.match(currentFieldName; parser.getDeprecationHandler())) {
 try {
 triggeredTime = WatcherDateTimeUtils.parseDateMath(currentFieldName; parser; ZoneOffset.UTC; clock);
 } catch (ElasticsearchParseException pe) {
 //Failed to parse as a date try datemath parsing
 throw new ElasticsearchParseException("could not parse [{}] trigger event for [{}] for watch [{}]. failed to parse " +
 "date field [{}]"; pe; ScheduleTriggerEngine.TYPE; context; watchId; currentFieldName);
 }
 } else if (Field.SCHEDULED_TIME.match(currentFieldName; parser.getDeprecationHandler())) {
 try {
 scheduledTime = WatcherDateTimeUtils.parseDateMath(currentFieldName; parser; ZoneOffset.UTC; clock);

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content