Missing exporter type for ” + name + ” exporter – Elasticsearch Error How To Solve Related Issues

Missing exporter type for ” + name + ” exporter – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch 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 causing many errors 


This guide will help you check for common problems that cause the log “missing exporter type for ” + name + ” exporter” 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 discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation). 

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 + "]");

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 how to move elasticsearch data from one server to another -views 103,922 ,score 90

How I can visualize elasticsearch metrics in prometheus?, both installed in a gke cluster -views   94

Find Configuration Errors

Analyze Now