[
https://issues.apache.org/jira/browse/AMBARI-24950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16698972#comment-16698972
]
ASF GitHub Bot commented on AMBARI-24950:
-----------------------------------------
kasakrisz edited a comment on issue #41: AMBARI-24950 - Logsearch: use os
timezone in Logfeeder
URL: https://github.com/apache/ambari-logsearch/pull/41#issuecomment-441645957
@adoroszlai
You are right, the grok pattern TZ can not parse values in the format like
`+0530`. However RFC 822 allows it.
This patch does not affect this behavior and we plan to fix it in another
patch.
I tested this patch setting the time zone of the nodes to `Asia/Kolkata` and
it works.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> 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)
