Failed to parse wildcard service – 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 Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” failed to parse wildcard service ” 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 wildcard service [{}]”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

String name = parser.currentName();
 final XContentLocation location = parser.getTokenLocation();
 try {
 services.put(name; WildcardServiceProvider.parse(parser));
 } catch (Exception e) {
 throw new ParsingException(location; "failed to parse wildcard service [{}]"; e; name);
 XContentParserUtils.ensureExpectedToken(XContentParser.Token.END_OBJECT; parser.currentToken(); parser::getTokenLocation); 
 XContentParserUtils.ensureExpectedToken(XContentParser.Token.END_OBJECT; parser.nextToken(); parser::getTokenLocation);


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content