Log rest authenticationsuccesst realm= uri= params= – How To Solve Related Issues


Log rest authenticationsuccesst realm= uri= params= – How To Solve Related Issues

Opster Team

Jan-20, Version: 1.7-8.0

 

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” rest authenticationsuccesst realm= uri= params= ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

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());
            }
        }
    }





 

Optimize Elasticsearch Performance

Try The Tool