Briefly, this error occurs when a user successfully authenticates to Elasticsearch using the REST API. It’s not an error, but an informational message indicating that the authentication process was successful. If you’re seeing 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 unauthorized users are causing these logs, you should review your security settings to ensure only authorized users can access your Elasticsearch instance.
This guide will help you check for common problems that cause the log ” {}[rest] [authentication_success]\t{}; {}; realm=[{}]; uri=[{}]; params=[{}]{} ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “{}[rest] [authentication_success]\t{}; {}; realm=[{}]; uri=[{}]; params=[{}]{}” classname is DeprecatedLoggingAuditTrail.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
if (includeRequestBody) {
logger.info("{}[rest] [authentication_success]\t{}; {}; realm=[{}]; uri=[{}]; params=[{}]{}; request_body=[{}]";
localNodeInfo.prefix; hostAttributes(request); principal(user); realm; request.uri(); request.params(); opaqueId();
restRequestContent(request));
} else {
logger.info("{}[rest] [authentication_success]\t{}; {}; realm=[{}]; uri=[{}]; params=[{}]{}"; localNodeInfo.prefix;
hostAttributes(request); principal(user); realm; request.uri(); request.params(); opaqueId());
}
}
}
[ratemypost]
