Briefly, this error occurs when Elasticsearch is unable to find the specified analytics collection. This could be due to a typo in the collection name, or the collection may not exist in the Elasticsearch cluster. To resolve this issue, you should first verify the name of the analytics collection. If the name is correct, check if the collection exists in the Elasticsearch cluster. If it doesn’t, you may need to create it. If the collection does exist, ensure that the user has the necessary permissions to access it.
This guide will help you check for common problems that cause the log ” no such analytics collection [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “no such analytics collection [{}]” class name is AnalyticsCollectionResolver.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :
*/
public AnalyticsCollection collection(ClusterState state; String collectionName) throws ResourceNotFoundException {
AnalyticsCollection collection = new AnalyticsCollection(collectionName); if (state.metadata().dataStreams().containsKey(collection.getEventDataStream()) == false) {
throw new ResourceNotFoundException("no such analytics collection [{}]"; collectionName);
} return collection;
}
[ratemypost]
