[jira] [Resolved] (FLUME-431) Add attribute with dir path to events produced by tailing sources

["Alexander Lorenz-Alten (Resolved) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLUME-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander Lorenz-Alten resolved FLUME-431.
------------------------------------------

    Resolution: Won't Fix
      Assignee:     (was: Alex Baranau)
    
> Add attribute with dir path to events produced by tailing sources
> -----------------------------------------------------------------
>
>                 Key: FLUME-431
>                 URL: https://issues.apache.org/jira/browse/FLUME-431
>             Project: Flume
>          Issue Type: Improvement
>          Components: Sinks+Sources
>    Affects Versions: v0.9.4
>            Reporter: Alex Baranau
>            Priority: Minor
>
> Currently tailing sources (tail, taildir) add attribute with filename to event. Looks like we should put dir names too, since this can be critical info for event's processing logic.
> E.g. tailing collectD output - it outputs stats data into dirs like /ubuntu904desktop.localdomain/cpu-0, /ubuntu904desktop.localdomain/cpu-1, etc. Here, path info is important for logs processing logic and should be available too.
> Jon's suggestion:
> My suggestion is to use a kwarg to make recording the dir a open, and to give the user option to pick attribute name.
> So something like this:
> tailDir("/dir",".*", 0, dirAttr="tailfiledir", fileAttr="tailfilename")
> So a file /dir/file would produce events with metadata like:
> event { taildirfile="/dir", tailfilename="file" }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira