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.
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 TransportPutRoleAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
if (validationException != null) {
listener.onFailure(validationException);
} else {
rolesStore.putRole(request; request.roleDescriptor(); listener.delegateFailure((l; created) -> {
if (created) {
logger.info("added role [{}]"; request.name());
} else {
logger.info("updated role [{}]"; request.name());
}
l.onResponse(new PutRoleResponse(created));
}));
