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

Opster Team

Aug-23, Version: 6.8-6.8

Briefly, this error occurs when Elasticsearch lacks the necessary permissions to index an audit event. This could be due to incorrect user roles, insufficient access rights, or a misconfigured security setting. To resolve this issue, you can: 1) Verify and update the user roles and permissions to ensure they have the necessary access rights. 2) Check and correct the security settings in Elasticsearch. 3) Ensure that the Elasticsearch cluster has the necessary resources to perform the indexing operation.

This guide will help you check for common problems that cause the log ” failed to index audit event: [access_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: [access_denied]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                final String lookRealmName = authentication.getLookedUpBy() == null ? null : authentication.getLookedUpBy().getName();
                final String[] roleNames = (String[]) authorizationInfo.asMap().get(LoggingAuditTrail.PRINCIPAL_ROLES_FIELD_NAME);
                enqueue(message("access_denied"; action; authentication.getUser(); roleNames; new Tuple(authRealmName; lookRealmName);
                        indices(message); message); "access_denied");
            } catch (final Exception e) {
                logger.warn("failed to index audit event: [access_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?