Index template matching request name not found – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.8-8.9

Briefly, this error occurs when Elasticsearch tries to find an index template that matches the specified name, but it doesn’t exist. This could be due to a typo in the template name or the template was not created. To resolve this issue, you can either create a new index template with the specified name or correct the name if it was misspelled. Also, ensure that the template is created in the correct cluster if you’re working with multiple Elasticsearch clusters.

This guide will help you check for common problems that cause the log ” index template matching [” + + “] not found ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: template, admin, indices, request, index.

Log Context

Log “index template matching [” + + “] not found” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 } else if (allTemplates.containsKey(name)) {
 results.put(name; allTemplates.get(name));
 } else {
 throw new ResourceNotFoundException("index template matching [" + + "] not found");
 if (request.includeDefaults() && DataLifecycle.isEnabled()) {
 new GetComposableIndexTemplateAction.Response(


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?