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

Opster Team

Aug-23, Version: 6.8-6.8

Briefly, this error occurs when Elasticsearch fails to index an audit event due to insufficient permissions. This could be due to incorrect user roles or privileges. To resolve this issue, you can check the user’s roles and permissions to ensure they have the necessary access to index audit events. Alternatively, you may need to review your Elasticsearch security settings or audit logging configurations. It’s also possible that the index is read-only, in which case you would need to change its settings to allow write operations.

This guide will help you check for common problems that cause the log ” failed to index audit event: [run_as_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: [run_as_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("run_as_denied"; action; authentication.getUser(); roleNames; new Tuple(authRealmName; lookRealmName);
                        null; message); "run_as_denied");
            } catch (final Exception e) {
                logger.warn("failed to index audit event: [run_as_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?