Failed to index audit event: tamperedrequest – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Failed to index audit event: tamperedrequest ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index and plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “Failed to index audit event: [tampered_request]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

     public void tamperedRequest(String requestId; String action; TransportMessage message) {
        if (events.contains(TAMPERED_REQUEST)) {
            try {
                enqueue(message("tampered_request"; action; (User) null; null; null; indices(message); message); "tampered_request");
            } catch (Exception e) {
                logger.warn("failed to index audit event: [tampered_request]"; e);



Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content