[
https://issues.apache.org/jira/browse/NIFI-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856036#comment-15856036
]
Pierre Villard commented on NIFI-1503:
--------------------------------------
For this one, I believe this is just a matter of logback configuration:
https://logback.qos.ch/manual/layouts.html#conversionWord
logback.xml configuration file should be updated by user to correctly define
the layout with something like (for instance):
{code}
%date{HH:mm:ss.SSS, Australia/Perth}
{code}
This would need to be updated where we have:
{code}
<encoder class="ch.qos.logback.classic.encoder.PatternLayoutEncoder">
<pattern>%date %level [%thread] %logger{40} %msg%n</pattern>
</encoder>
{code}
But IMO, this is something that users should perform on their own when
installing NiFi, no?
> Include timezone on NiFI log messages
> -------------------------------------
>
> Key: NIFI-1503
> URL: https://issues.apache.org/jira/browse/NIFI-1503
> Project: Apache NiFi
> Issue Type: Improvement
> Affects Versions: 0.4.1
> Reporter: Matthew Clarke
> Assignee: Andre
> Priority: Minor
>
> While we can stress the importance of using NTP to make sure clocks across
> multiple system running NIFi remain in sync, we cannot enforce a requirement
> that all system set their systems to a common timezone. The logs currently
> do not show the timezone on each log entry which can make it confusing for
> users when trying to trace log events across multiple NiFI instances that are
> configured for different timezones. This would be increasing difficult if
> logs were moved to a central logging server.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)