----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74519/#review225607 -----------------------------------------------------------
Ship it! Ship It! - Ramachandran Krishnan On July 18, 2023, 12:23 p.m., Prashant Satam wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74519/ > ----------------------------------------------------------- > > (Updated July 18, 2023, 12:23 p.m.) > > > Review request for ranger and Madhan Neethiraj. > > > Bugs: RANGER-4321 > https://issues.apache.org/jira/browse/RANGER-4321 > > > Repository: ranger > > > Description > ------- > > As mentioned in RANGER-4024, the expected behavior is: > when request-id is added in log pattern and RangerMDCFilter is enabled via > property, > when the request header contains request-id, request-id should be available > in all the ranger admin logs. I tried to enable RangerMDCFilter by adding in > web.xml, but it did not work. > > > Diffs > ----- > > security-admin/src/main/resources/conf.dist/security-applicationContext.xml > 807791f28 > > > Diff: https://reviews.apache.org/r/74519/diff/1/ > > > Testing > ------- > > Added ranger.admin.mdc-filter.enabled to enable RangerMDCFilter and added > RangerMDCFilter in security-applicationContext.xml to get it in execution > order ,Also edited pattern FIELD for logs in logback.xml File as mentioned in > RANGER 4024 > > > Thanks, > > Prashant Satam > >
