[
https://issues.apache.org/jira/browse/FLUME-1782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13603535#comment-13603535
]
Edward Sargisson edited comment on FLUME-1782 at 3/15/13 5:15 PM:
------------------------------------------------------------------
Hi Israel,
Well, if you changed the timezone then the output will not work with Kibana so
this wouldn't be a terribly wise thing to do. However, I have written the code
to do it and updated the docs with the details - as well as fixing
capitalization and heading level issues. That code is now attached as
flume-1782-3.patch which needs to be added on to flume-1782-2.patch.
was (Author: ejsarge):
Hi Israel,
Well, if you changed the timezone then the output will not work with Kibana so
this wouldn't be a terribly wise thing to do. However, I have written the code
to do it and updated the docs with the details - as well as fixing
capitalization and heading level issues.
> Elastic Search sink does not use UTC to determine the correct index to write
> to.
> --------------------------------------------------------------------------------
>
> Key: FLUME-1782
> URL: https://issues.apache.org/jira/browse/FLUME-1782
> Project: Flume
> Issue Type: Bug
> Components: Sinks+Sources
> Reporter: Edward Sargisson
> Fix For: v1.4.0
>
> Attachments: flume-1782-2.patch, flume-1782-3.patch, flume-1782.patch
>
>
> The GUI for logs in ElasticSearch, Kibana, uses the utc date to determine
> which index to read for a search. The Flume ElasticSearch sink is using the
> local timezone to determine which index to write to. This means that events
> are being placed in the incorrect index and Kibana doesn't always find them.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
