You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ranger.apache.org by "Ramesh Mani (Jira)" <ji...@apache.org> on 2021/10/13 05:26:00 UTC

[jira] [Updated] (RANGER-3478) Remove INFO level auditing logs in the Ranger audit frame to reduce verbosity

     [ https://issues.apache.org/jira/browse/RANGER-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ramesh Mani updated RANGER-3478:
--------------------------------
    Attachment: 0001-RANGER-3478-Remove-INFO-level-auditing-logs-in-the-R.patch

>  Remove INFO level auditing logs in the Ranger audit frame to reduce verbosity 
> -------------------------------------------------------------------------------
>
>                 Key: RANGER-3478
>                 URL: https://issues.apache.org/jira/browse/RANGER-3478
>             Project: Ranger
>          Issue Type: Bug
>          Components: Ranger
>    Affects Versions: 3.0.0
>            Reporter: Ramesh Mani
>            Priority: Minor
>         Attachments: 0001-RANGER-3478-Remove-INFO-level-auditing-logs-in-the-R.patch
>
>
> There are logs which are created as part of audit framework which are in INFO level. These  are generate at a quick pace resulting in huge service logs files. By converting them to debug level, Service log will be much cleaner. To get ranger plugin logs we can always put Ranger Package / classes in debug in log4j properties for each of services.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)