You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Qiang Zhang (JIRA)" <ji...@apache.org> on 2017/04/25 02:25:04 UTC

[jira] [Commented] (RANGER-1540) Log is very important for big data platform. The main purpose of log analysis is that we need to know who is running the service, in which machine running service, which service out of the problem. The ranger security admin should support the feature.

    [ https://issues.apache.org/jira/browse/RANGER-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15982291#comment-15982291 ] 

Qiang Zhang commented on RANGER-1540:
-------------------------------------

The function is very useful. With this feature, we can get following information directly from log file:
1. who is running the Ranger.
2. In which machine running the Ranger.
3. What is the problem for the Ranger.


> Log is very important for big data platform. The main purpose of log analysis is that we need to know who is running the service, in which machine running service, which service out of the problem. The ranger security admin should support the feature.
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: RANGER-1540
>                 URL: https://issues.apache.org/jira/browse/RANGER-1540
>             Project: Ranger
>          Issue Type: New Feature
>          Components: admin
>            Reporter: peng.jianhua
>            Assignee: peng.jianhua
>              Labels: patch
>         Attachments: 0001-RANGER-1540-Log-is-very-important-for-big-data-platf.patch
>
>
> Log is very important for big data platform. The main purpose of log analysis is that we need to know who is running the service, in which machine running service, which service out of the problem. The ranger security admin should support the feature.
> Implement logic:
> 1. Modify the value of log4j.appender.xa_log_appender.file from ${logdir}/ranger_admin.log to ${logdir}/ranger-${user}-rangeradmin-${hostname}.log in /security-admin/src/main/webapp/WEB-INF/log4j.properties file.
> 2. Pass ${user} and ${hostname} as parameters to org.apache.ranger.server.tomcat.EmbeddedServer.
> 3. User obtains the user and hostname information by parsing the log file name.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)