[
https://issues.apache.org/jira/browse/STORM-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14185792#comment-14185792
]
ASF GitHub Bot commented on STORM-540:
--------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/301
> Change default time format in logs to ISO8601 in order to include timezone
> --------------------------------------------------------------------------
>
> Key: STORM-540
> URL: https://issues.apache.org/jira/browse/STORM-540
> Project: Apache Storm
> Issue Type: Improvement
> Reporter: Michael Pershyn
> Assignee: Michael Pershyn
> Priority: Trivial
> Fix For: 0.9.3-rc2
>
>
> Now default time format in logback/cluster.xml is:
> {code}
> <pattern>%d{yyyy-MM-dd HH:mm:ss} %c{1} [%p] %m%n</pattern>
> {code}
> It is human-readable, but does not include timezone, and cluster log files
> configuration have to be changed for error-free machine processing, for
> example using Logstash->ElasticSearch->Kibana pipeline.
> If some of the cluster nodes time is not correctly configured it will take
> lots of time to find out an issue with topology. Especially if there is such
> a pipeline and time is converted from times in logs (in host timezones) to
> timestamps (in UTC).
> I have checked out time formats, the most reasonable seems to be
> [ISO8601|http://en.wikipedia.org/wiki/ISO_8601]. It has all the fields,
> timezone, is similar to format that is currently used, but is a standard and
> is widely supported.
> In regards to logging pipelines, logstash's grok [has out of the
> box|http://grokdebug.herokuapp.com/patterns#] rule for TIMESTAMP_ISO8601.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
