Analytics collection does not exists - Common causes and quick fixes

Analytics collection does not exists – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 8.8-8.9

Briefly, this error occurs when Elasticsearch tries to access an analytics collection that does not exist. This could be due to a typo in the collection name, or the collection may have been deleted or not yet created. To resolve this issue, you can check the collection name for typos, ensure the collection exists, or create the collection if it doesn’t exist. If the collection was deleted, you may need to restore it from a backup.

This guide will help you check for common problems that cause the log ” analytics collection [{}] does not exists ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “analytics collection [{}] does not exists” class name is AnalyticsCollectionService.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 AnalyticsCollection collection = new AnalyticsCollection(request.getCollectionName());
 DeleteDataStreamAction.Request deleteDataStreamRequest = new DeleteDataStreamAction.Request(collection.getEventDataStream());
 ActionListener deleteDataStreamListener = ActionListener.wrap(listener::onResponse; (Exception e) -> {
 if (e instanceof ResourceNotFoundException) {
 listener.onFailure(new ResourceNotFoundException("analytics collection [{}] does not exists"; request.getCollectionName()));
 return;
 }  e = new ElasticsearchStatusException(
 "error while deleting analytics collection [{}]";