Briefly, this error occurs when Elasticsearch encounters an unknown logging level in the logging configuration. Logging levels control the amount of detail outputted in logs. If an invalid level is specified, Elasticsearch cannot parse it. To resolve this, check your logging configuration and ensure that the logging level is set to a valid value. Valid logging levels include: ERROR, WARN, INFO, DEBUG, TRACE. Correct the logging level and restart Elasticsearch for the changes to take effect.
This guide will help you check for common problems that cause the log ” failed to parse [{}] action [{}/{}]. unknown logging level [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “failed to parse [{}] action [{}/{}]. unknown logging level [{}]” class name 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);
[ratemypost]
