[jira] [Comment Edited] (KNOX-1147) KNOX Audit Log time not configurable or not supporting TZ
[
https://issues.apache.org/jira/browse/KNOX-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16531516#comment-16531516
]
Larry McCay edited comment on KNOX-1147 at 7/3/18 2:58 PM:
---
Pushing this out due to quick review and resulting questions:
* Why hardcode PST?
* Should we use zulu time [1] which would include the difference from GMT and
help differentiate which TZ a log is actually from?
was (Author: lmccay):
Pushing this out again due to quick review and resulting questions:
* Why hardcode PST?
* Should we use zulu time [1] which would include the difference from GMT and
help differentiate which TZ a log is actually from?
> 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
>Priority: Major
> Fix For: 1.2.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
(v7.6.3#76005)
[jira] [Comment Edited] (KNOX-1147) KNOX Audit Log time not configurable or not supporting TZ
[
https://issues.apache.org/jira/browse/KNOX-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290033#comment-16290033
]
Rajesh Chandramohan edited comment on KNOX-1147 at 12/13/17 10:38 PM:
--
[~lmccay]
Please Review the attached changes , Can work on enhanced version to merge with
v15 too.
was (Author: rajeshhadoop):
Please check the attached changes.
> 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)
