[ https://issues.apache.org/jira/browse/KNOX-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rajesh Chandramohan updated KNOX-1147: -------------------------------------- Attachment: KNOX-1147.patch Adding a patch, which helps with this case. We can extend further by giving the Configurable variable for layout through log4j.properties as like log4j.EnhancedPatternLayout > KNOX Audit Log time not configurable or not supporting TZ > --------------------------------------------------------- > > Key: KNOX-1147 > URL: https://issues.apache.org/jira/browse/KNOX-1147 > Project: Apache Knox > Issue Type: Improvement > Affects Versions: 0.10.0, 0.13.0, 0.14.0 > Reporter: Rajesh Chandramohan > Fix For: 0.15.0 > > Attachments: KNOX-1147.patch > > > The KNOX Log4J configuration for Knoxaudit log uses > or.hadoop.gateway.audit.log4j.layout.AuditLayout , so when the system is > using PST tz , The auditLog is logging with 1hr ahead of current PST time. Is > there a way to log audit event matching with current time in system and not > break with DST change? > Even in latest version it is having hardcoded time pattern , not able to add > Time zone. Was thinking of adding > setDateFormat(DATE_FORMAT, TimeZone.getTimeZone(TZ)); But is there any other > better way to get around this issue? > +++++ > public class AuditLayout extends DateLayout { > > private static final String DATE_FORMAT = "yy/MM/dd HH:mm:ss"; > private static final String SEPARATOR = "|"; > private StringBuffer sb = new StringBuffer(); > Override > public void activateOptions() { > setDateFormat( DATE_FORMAT ); > } > +++++ > Thanks -- This message was sent by Atlassian JIRA (v6.4.14#64029)