Missing exporter type for ” + name + ” exporter – 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 ” missing exporter type for ” + name + ” exporter ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “missing exporter type for [” + name + “] exporter”classname  is Exporters.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

Settings exportersSettings = settings.getByPrefix("xpack.monitoring.exporters.");
 for (String name : exportersSettings.names()) {
 Settings exporterSettings = exportersSettings.getAsSettings(name);
 String type = exporterSettings.get("type");
 if (type == null) {
 throw new SettingsException("missing exporter type for [" + name + "] exporter");
 Exporter.Factory factory = factories.get(type);
 if (factory == null) {
 throw new SettingsException("unknown exporter type [" + type + "] set for exporter [" + name + "]");


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content