[jira] [Updated] (RANGER-1692) Similar to RANGER-1540, the Ranger kms should also support the same new feature.

["peng.jianhua (JIRA)" <ji...@apache.org>]

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

peng.jianhua updated RANGER-1692:
---------------------------------
    Attachment: 0001-RANGER-1692-Similar-to-RANGER-1540-the-Ranger-kms-sh.patch

> Similar to RANGER-1540, the Ranger kms should also support the same new feature.
> --------------------------------------------------------------------------------
>
>                 Key: RANGER-1692
>                 URL: https://issues.apache.org/jira/browse/RANGER-1692
>             Project: Ranger
>          Issue Type: New Feature
>          Components: kms
>            Reporter: peng.jianhua
>            Assignee: peng.jianhua
>            Priority: Minor
>              Labels: newbie, patch
>         Attachments: 0001-RANGER-1692-Similar-to-RANGER-1540-the-Ranger-kms-sh.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 kms should support the feature.
> Implement logic:
> 1. Modify the value of kms-log4j.log4j.appender.kms.File from ${kms.log.dir}/kms.log to ${logdir}/ranger-${user}-kms-${hostname}.log in kms-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.4.14#64029)