Missing exporter type for name exporter – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch is unable to find the specified exporter type for a monitoring configuration. This could be due to a typo in the exporter name or the exporter plugin is not installed. To resolve this issue, you can check the spelling of the exporter name in your configuration file. If it’s correct, ensure that the required exporter plugin is installed and enabled. If not, install the necessary plugin and restart Elasticsearch.

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” class name is Exporters.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 Settings exportersSettings = settingsToUse.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 + "]");


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?