Failed to parse action /. failed to parse field – 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 ” failed to parse action /. failed to parse field ” 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 “failed to parse [{}] action [{}/{}]. failed to parse [{}] field”classname  is JiraAction.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

proxy = HttpProxy.parse(parser);
 } else if (Field.FIELDS.match(currentFieldName; parser.getDeprecationHandler())) {
 try {
 fields = parser.map();
 } catch (Exception e) {
 throw new ElasticsearchParseException("failed to parse [{}] action [{}/{}]. failed to parse [{}] field"; e; TYPE;
 watchId; actionId; Field.FIELDS.getPreferredName());
 }
 } else {
 throw new ElasticsearchParseException("failed to parse [{}] action [{}/{}]. unexpected token [{}/{}]"; TYPE; watchId;
 actionId; token; currentFieldName);

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content