You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Israel Ekpo (JIRA)" <ji...@apache.org> on 2013/03/15 01:02:15 UTC

[jira] [Commented] (FLUME-1782) Elastic Search sink does not use UTC to determine the correct index to write to.

    [ https://issues.apache.org/jira/browse/FLUME-1782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13602910#comment-13602910 ] 

Israel Ekpo commented on FLUME-1782:
------------------------------------

It think it would be helpful if the user can configure what timezone or offset they wish to use.

This way the logic is not tied only to UTC. 

You can use Eastern Time, Mountain Time, Pacific Time or whichever timezone you prefer.

Any thoughts?
                
> 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.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