Failed to index audit event connection denied – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-6.8

Briefly, this error occurs when Elasticsearch is unable to index an audit event due to a connection issue. This could be due to network problems, insufficient permissions, or a misconfigured Elasticsearch cluster. To resolve this issue, you can check the network connectivity, ensure that Elasticsearch has the necessary permissions to perform the operation, and verify the cluster configuration. Additionally, check the Elasticsearch logs for more detailed error messages that can help identify the root cause of the problem.

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

Log Context

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

    public void connectionDenied(InetAddress inetAddress; String profile; SecurityIpFilterRule rule) {
        if (events.contains(CONNECTION_DENIED)) {
            try {
                enqueue(message("ip_filter"; "connection_denied"; inetAddress; profile; rule); "connection_denied");
            } catch (Exception e) {
                logger.warn("failed to index audit event: [connection_denied]"; e);



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?