[jira] [Commented] (NIFI-1503) Include timezone on NiFI log messages
[ https://issues.apache.org/jira/browse/NIFI-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776909#comment-17776909 ] Pierre Villard commented on NIFI-1503: -- Yeah I agree with Mark. I don't think we should change the default here and I'd leave this up to the user depending on their requirements. I'll close the JIRA and remove the 2.0.0 fix version. Please reopen if someone feels strongly about this. > 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 >Priority: Minor > Labels: Breaking-Change > Fix For: 2.0.0 > > > 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 (v8.20.10#820010)
[jira] [Commented] (NIFI-1503) Include timezone on NiFI log messages
[ https://issues.apache.org/jira/browse/NIFI-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776901#comment-17776901 ] Mark Payne commented on NIFI-1503: -- While I can see how this would be advantageous in a production deployment, we generally skew toward setting NiFi defaults as would be appropriate for local deployments on laptops, etc. It should be expected that for production deployments that configs should be changed. I do not think we should change the default values to UTC, as it makes the logs more difficult to read for "local" non-production use cases. > 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 >Priority: Minor > Labels: Breaking-Change > Fix For: 2.0.0 > > > 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 (v8.20.10#820010)
[jira] [Commented] (NIFI-1503) Include timezone on NiFI log messages
[ https://issues.apache.org/jira/browse/NIFI-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15856093#comment-15856093 ] Andre commented on NIFI-1503: - [~pvillard] agreed, specially because the behavior can be changed locally by following the steps above. > 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 > Labels: Breaking-Change > > 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)
[jira] [Commented] (NIFI-1503) Include timezone on NiFI log messages
[ https://issues.apache.org/jira/browse/NIFI-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15856052#comment-15856052 ] Pierre Villard commented on NIFI-1503: -- I don't see any objection to set UTC as a default timezone. However, I believe this would be a breaking change that needs to wait a major release. If people developed flows to parse NiFi logs or configured third-party tools to analyze/monitor NiFi logs, this could be an issue, don't you think? > 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)
[jira] [Commented] (NIFI-1503) Include timezone on NiFI log messages
[ https://issues.apache.org/jira/browse/NIFI-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15856047#comment-15856047 ] Andre commented on NIFI-1503: - [~pvillard] that was my guess as well (logback) but I agree with the Matthew. We should add a timezone, even if that timezone happens to be UTC (the best choice for a locale agnostic timestamp IMHO) > 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)
[jira] [Commented] (NIFI-1503) Include timezone on NiFI log messages
[
https://issues.apache.org/jira/browse/NIFI-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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}
%date %level [%thread] %logger{40} %msg%n
{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)
