Added role – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when a new role is added to Elasticsearch. This could be due to a change in the configuration file or through the API. It’s not necessarily an error, but more of an informational message. If it’s unintended, you should review your security settings. To resolve this, you can remove the role if it’s not needed, or adjust the permissions if they’re not correct. Also, ensure that only authorized personnel have access to make such changes to prevent unauthorized role additions.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” added role [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “added role [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        if (validationException != null) {
        } else {
            rolesStore.putRole(request; request.roleDescriptor(); listener.delegateFailure((l; created) -> {
                if (created) {
          "added role [{}]";;
                } else {
          "updated role [{}]";;
                l.onResponse(new PutRoleResponse(created));


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?