nevzheng opened a new issue, #13109: URL: https://github.com/apache/gravitino/issues/13109
### What would you like to be improved? `GravitinoInterceptionService` logs a full stack trace at WARN every time a caller is rejected because they are not a member of the metalake (`ForbiddenException` from `AuthorizationUtils.checkCurrentUser`). This is a client-driven 403, so a busy deployment can write a stack trace per rejected request. The throwable was added to that WARN in #13057 so the cause stays in the server log when stack traces are omitted from responses. The same PR does not log other client errors on the authentication path (401/403/400), so the two paths now treat client errors differently. This needs a closer look, and was left out of #13057 to keep that PR's scope tight. ### How should we improve? Open questions: - Should client-driven 403s on the authorization path log the stack trace, the message only, or log the stack at DEBUG? - Should the authentication and authorization paths follow one rule for which failures are logged with a stack trace? Location: `server/src/main/java/org/apache/gravitino/server/web/filter/GravitinoInterceptionService.java`, `catch (ForbiddenException ex)` in the metadata authorization interceptor. Related: #12728, #13057. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
