How To Solve Issues Related to Log – transport accessgrantedt; ; roles=; action=; indices=; request=

How To Solve Issues Related to Log – transport accessgrantedt; ; roles=; action=; indices=; request=

Updated: Jan-20

Elasticsearch Version: 1.7-8.0

Background

Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.


To troubleshoot log “transport accessgrantedt; ; roles=; action=; indices=; request=” it’s important to understand a few problems related to Elasticsearch concepts plugin. See bellow important tips and explanations on these concepts

Log Context

Log”{}[transport] [access_granted]t{}; {}; roles=[{}]; action=[{}]; indices=[{}]; request=[{}]{}” classname is DeprecatedLoggingAuditTrail.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             if (eventFilterPolicyRegistry.ignorePredicate().test(new AuditEventMetaInfo(Optional.of(user);
                    Optional.of(effectiveRealmName(authentication)); Optional.of(authorizationInfo); indices)) == false) {
                final LocalNodeInfo localNodeInfo = this.localNodeInfo;
                final String[] roleNames = (String[]) authorizationInfo.asMap().get(LoggingAuditTrail.PRINCIPAL_ROLES_FIELD_NAME);
                if (indices.isPresent()) {
                    logger.info("{}[transport] [access_granted]\t{}; {}; roles=[{}]; action=[{}]; indices=[{}]; request=[{}]{}";
                            localNodeInfo.prefix; originAttributes(threadContext; message; localNodeInfo); subject(authentication);
                            arrayToCommaDelimitedString(roleNames); action; arrayToCommaDelimitedString(indices.get());
                            message.getClass().getSimpleName(); opaqueId());
                } else {
                    logger.info("{}[transport] [access_granted]\t{}; {}; roles=[{}]; action=[{}]; request=[{}]{}"; localNodeInfo.prefix;




Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Log Users And Query In Audit Log  

Github Issue Number 31046  

About Opster

Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance

Find Configuration Errors

Analyze Now