Failed to parse action /. unknown logging level – Elasticsearch Error How To Solve Related Issues

Failed to parse action /. unknown logging level – Elasticsearch Error How To Solve Related Issues

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

category = parser.text();
  } else if (Field.LEVEL.match(currentFieldName; parser.getDeprecationHandler())) {
  try {
  level = LoggingLevel.valueOf(parser.text().toUpperCase(Locale.ROOT));
  } catch (IllegalArgumentException iae) {
  throw new ElasticsearchParseException("failed to parse [{}] action [{}/{}]. unknown logging level [{}]"; TYPE;
  watchId; actionId; parser.text());
  }
  } else {
  throw new ElasticsearchParseException("failed to parse [{}] action [{}/{}]. unexpected string field [{}]"; TYPE;
  watchId; actionId; currentFieldName);

 

Optimize Elasticsearch Performance

Try The Tool