Unregistered Aggregation registryKey getName – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.1-8.4

Briefly, this error occurs when Elasticsearch tries to execute an aggregation that is not registered in its system. This could be due to a typo in the aggregation name or using an aggregation that is not supported in the current version of Elasticsearch. To resolve this issue, you should verify the aggregation name and ensure it is correctly spelled and supported in your Elasticsearch version. If you’re using a custom aggregation, ensure it is properly registered.

This guide will help you check for common problems that cause the log ” Unregistered Aggregation [” + registryKey.getName() + “] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: aggregations, search.

Log Context

Log “Unregistered Aggregation [” + registryKey.getName() + “]” class name is ValuesSourceRegistry.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 valuesSourceConfig.getDescription() + " is not supported for aggregation [" + registryKey.getName() + "]"
 return supplier;
 throw new AggregationExecutionException("Unregistered Aggregation [" + registryKey.getName() + "]");
 }  public AggregationUsageService getUsageService() {
 return usageService;


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?