you can try it out. I am not really sure. But, I am having trouble seeing
your reasoning here. Say some external application creates such log files
for you every night at 12 AM, then basically you want to ignore all the
remaining data until 11.59 without passing them over to flume?

Thanks & Regards
Rajalakshmi (Raji) Ramesh
-------------------------------------------------------
Graduate Student
Georgia Institute of Technology
Atlanta, GA
-------------------------------------------------------



On Thu, May 17, 2012 at 6:41 PM, M@he$h <mahesh...@gmail.com> wrote:

> Hello Raji,
>
> Thanks for the reply.
>
> so using flume's *tailDir *, we cannot achieve what I want is it?
>
> does something like below will work or not?
>
> *tailDir("/usr/local/current/logs/", "rls.log.%M%d%Y" , "true")
> *
>
>
> On Thu, May 17, 2012 at 6:35 PM, Rajalakshmi Ramesh <
> rrajalaks...@gatech.edu> wrote:
>
>> I would suggest moving that intelligence to a cron job by removing log
>> files that ypu dont want to be tail at the end of the day. Will make your
>> configuration much easier.
>>
>>
>> alakshmi (Raji) Ramesh
>> -------------------------------------------------------
>> Graduate Student
>> Georgia Institute of Technology
>> Atlanta, GA
>> -------------------------------------------------------
>>
>>
>>
>> On Thu, May 17, 2012 at 6:31 PM, M@he$h <mahesh...@gmail.com> wrote:
>>
>>> Hello,
>>>
>>> We have a directory where there will be log files for each day being
>>> written. for example :
>>>
>>> abc.log.05162012
>>> pqr.log.05162012
>>> abc.log.05172012
>>> pqr.log.05172012
>>>
>>>
>>> I want flume to tail files depending on that day's date. for example :
>>> as today's date is 05/17/2012 , it should only tail file names which have
>>> 05172012 at the end.
>>>
>>> Can we do it using tailDir? or can you suggest the best way to do this
>>> in flume?
>>>
>>> Look forward for your response.
>>>
>>>
>>> --
>>> *Thanks and Regards,
>>> *
>>> Mahesh
>>> 619-816-7011.
>>>
>>
>>
>
>
> --
> *Thanks and Regards,
> *
> Mahesh
> 619-816-7011.
>

Reply via email to