[
https://issues.apache.org/jira/browse/AMBARI-24950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16699147#comment-16699147
]
Hudson commented on AMBARI-24950:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-LogSearch-master-Commit #51 (See
[https://builds.apache.org/job/Ambari-LogSearch-master-Commit/51/])
AMBARI-24950 - Logsearch: use os timezone in Logfeeder (#41) (oleewere:
[https://gitbox.apache.org/repos/asf?p=ambari-logsearch.git&a=commit&h=8ca63008dfc6da4d1ab73b277fe8d4c908f6825d])
* (edit)
ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/loglevelfilter/LogLevelFilterHandler.java
* (edit)
ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/util/DateUtil.java
> Logsearch: use os timezone in Logfeeder
> ---------------------------------------
>
> Key: AMBARI-24950
> URL: https://issues.apache.org/jira/browse/AMBARI-24950
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
> Affects Versions: 2.8.0
> Reporter: Krisztian Kasa
> Assignee: Krisztian Kasa
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
>
> Logfeeder sets the default timezone to GMT at start up. Most service logs'
> logtime are in os timezone. If os timezone is set to other than UTC Logfeeder
> does not convert the logtime values to UTC when sending the log entry to Solr
> and Logsearch portal shows invalid log time values.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
