Briefly, this error occurs when a user or client successfully authenticates with Elasticsearch’s transport layer. This is not an error but an informational message indicating that the authentication process was successful. If you see this message frequently and it’s causing noise in your logs, you can adjust the logging level to WARN or ERROR to suppress informational messages. Alternatively, if you’re not expecting this authentication, it could indicate an unauthorized access, in which case you should review your security settings and access controls.
This guide will help you check for common problems that cause the log ” {}[transport] [authentication_success]\t{}; {}; realm=[{}]; action=[{}]; indices=[{}]; request=[{}]{} ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “{}[transport] [authentication_success]\t{}; {}; realm=[{}]; action=[{}]; indices=[{}]; request=[{}]{}” classname is DeprecatedLoggingAuditTrail.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
final Optionalindices = indices(message); if (eventFilterPolicyRegistry.ignorePredicate() .test(new AuditEventMetaInfo(Optional.of(user); Optional.of(realm); Optional.empty(); indices)) == false) { final LocalNodeInfo localNodeInfo = this.localNodeInfo; if (indices.isPresent()) { logger.info("{}[transport] [authentication_success]\t{}; {}; realm=[{}]; action=[{}]; indices=[{}]; request=[{}]{}"; localNodeInfo.prefix; originAttributes(threadContext; message; localNodeInfo); principal(user); realm; action; arrayToCommaDelimitedString(indices.get()); message.getClass().getSimpleName(); opaqueId()); } else { logger.info("{}[transport] [authentication_success]\t{}; {}; realm=[{}]; action=[{}]; request=[{}]{}"; localNodeInfo.prefix; originAttributes(threadContext; message; localNodeInfo); principal(user); realm; action;
[ratemypost]