----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/60801/#review180413 -----------------------------------------------------------
Ship it! Ship It! - Colm O hEigeartaigh On July 13, 2017, 3:31 a.m., pengjianhua wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/60801/ > ----------------------------------------------------------- > > (Updated July 13, 2017, 3:31 a.m.) > > > Review request for ranger, Alok Lal, Ankita Sinha, Don Bosco Durai, Colm O > hEigeartaigh, Gautam Borad, Madhan Neethiraj, Ramesh Mani, Selvamohan > Neethiraj, Velmurugan Periasamy, and Qiang Zhang. > > > Bugs: RANGER-1692 > https://issues.apache.org/jira/browse/RANGER-1692 > > > Repository: ranger > > > Description > ------- > > 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-kms-${hostname}-${user}.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. > > > Diffs > ----- > > kms/config/kms-webapp/kms-log4j.properties 479b5b4 > kms/scripts/ranger-kms e902509 > > > Diff: https://reviews.apache.org/r/60801/diff/1/ > > > Testing > ------- > > > Thanks, > > pengjianhua > >
