Template must not be empty – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

Briefly, this error occurs when there is a syntax error in a dynamic template. Dynamic templates are used to define mappings for fields that match a specific pattern. To resolve the issue, review the dynamic template and correct any syntax errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

Take a self-guided product tour to see for yourself (no registration required).

This guide will help you check for common problems that cause the log ” Template must not be empty ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: template and plugin.


Log Context

Log “Template must not be empty”classname  is TemplateUtils.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

public static void validate(String source) {
 if (source == null) {
 throw new ElasticsearchParseException("Template must not be null");
 if (Strings.isEmpty(source)) {
 throw new ElasticsearchParseException("Template must not be empty");
 try {
 XContentHelper.convertToMap(JsonXContent.jsonXContent; source; false);
 } catch (Exception e) {


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content