Failed to put audit trail template – How to solve related issues

Failed to put audit trail template – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

In addition to reading this guide, we recommend you run the Elasticsearch Template Optimizer to fix problems in your data modeling.

It will analyze your templates to detect issues and improve search performance, reduce indexing bottlenecks and optimize storage utilization. The Template Optimizer is free and requires no installation.

This guide will help you check for common problems that cause the log to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts below. Advanced users might want to skip right to the common problems section in each concept or run the template optimizer.

Log Context

Log “Failed to put audit trail template” classname is IndexAuditTrail.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                         } else if (TemplateUtils.checkTemplateExistsAndVersionMatches(INDEX_TEMPLATE_NAME;
                                SECURITY_VERSION_STRING; clusterStateResponse.getState(); logger;
                                Version.CURRENT::onOrBefore) == false) {
                            putTemplate(customAuditIndexSettings(settings; logger);
                                    e -> {
                                        logger.error("failed to put audit trail template"; e);
                                        transitionStartingToInitialized();
                                    });
                        } else {
                            // for some reason we can't start up since the remote cluster is not fully setup. in this case
                            // we try to wait for yellow status (all primaries started up) this will also wait for




 

Run the Check-Up to get a customized report like this:

Analyze your cluster