Uploaded image for project: 'Flume'
  1. Flume
  2. FLUME-1782

Elastic Search sink does not use UTC to determine the correct index to write to.

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Won't Fix
    • None
    • None
    • Sinks+Sources
    • None

    Description

      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.

      Attachments

        1. flume-1782.patch
          7 kB
          Edward Sargisson
        2. FLUME-1782-1.4.0.patch
          10 kB
          Edward Sargisson
        3. FLUME-1782-1.4.0-1.patch
          9 kB
          Edward Sargisson
        4. FLUME-1782-1.4.0-2.patch
          11 kB
          Edward Sargisson
        5. FLUME-1782-1.4.0-3.patch
          19 kB
          Edward Sargisson
        6. FLUME-1782-1.4.0-4.patch
          34 kB
          Edward Sargisson
        7. flume-1782-2.patch
          8 kB
          Edward Sargisson
        8. flume-1782-3.patch
          12 kB
          Edward Sargisson
        9. FLUME-1782-FLUME-1972-1.4.0-1.patch
          54 kB
          Edward Sargisson

        Issue Links

          relates to

          Improvement - An improvement or enhancement to an existing feature or task. FLUME-2015 ElasticSearchSink: need access to IndexRequestBuilder instance during flume event processing

          • Major - Major loss of function.
          • Resolved
          links to

          Web Link Review Board

          Activity

            People

              ejsarge Edward Sargisson
              ejsarge Edward Sargisson
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: