# Input files with dynamic filename

**URL:** <https://discuss.elastic.co/t/input-files-with-dynamic-filename/42695>\
**Category:** Logstash\
**Created:** [February 25, 2016, 10:18am UTC](https://discuss.elastic.co/t/input-files-with-dynamic-filename/42695 "2016-02-25T10:18:07Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![sunilmchaudhari](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sunilmchaudhari/32/9475_2.png) [@sunilmchaudhari](https://discuss.elastic.co/u/sunilmchaudhari)\
**Post date:** [February 25, 2016, 10:18am UTC](https://discuss.elastic.co/t/input-files-with-dynamic-filename/42695/1 "2016-02-25T10:18:07Z")

</div>

Hi,  
We have some files in our systems, which has dynamic file names, date time appended.  
Example, server\_201602025 etc.  
FIle created today will neither be archived to some other location nor it will be appended any new data after 2016-02-25 . On next day new file will be created server\_201602026

Same file is the input for LSF. Now I want to know, If I read this file in LSF using /log\_dir/\* then LSF will maintain pointer/offset for all files at any instance of time T1. This is my understanding.  
How does it affects performance of LSF?  
Is there any way to skip older files which has no latest data after some time, may be some days. So that harvestor will stop keep watch of old files?

please clarify.

thanks  
Sunil

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [February 26, 2016, 1:31am UTC](https://discuss.elastic.co/t/input-files-with-dynamic-filename/42695/2 "2016-02-26T01:31:50Z")

</div>

You should use filebeat, LSF has been deprecated!

---

<div class="post-metadata">

**Author:** ![sunilmchaudhari](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sunilmchaudhari/32/9475_2.png) [@sunilmchaudhari](https://discuss.elastic.co/u/sunilmchaudhari)\
**Post date:** [March 2, 2016, 5:34am UTC](https://discuss.elastic.co/t/input-files-with-dynamic-filename/42695/3 "2016-03-02T05:34:47Z")

</div>

Hi Mark,  
Thanks for the reply.  
However, we are almost in the production.  
**Event pipeline is like** : LSF (Client) --\>(Server) Shipper--\>Redis--\>Broker--\>nGinx--\>ES

How complex or tough to replace LSF with filebeat?  
What changes we need to do on other sides, Shipper?

We do have one client with AIX. Do filebeat support AIX?

br,  
Sunil

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [March 2, 2016, 5:35am UTC](https://discuss.elastic.co/t/input-files-with-dynamic-filename/42695/4 "2016-03-02T05:35:44Z")

</div>

Beats don't support AIX as it doesn't support go.

Otherwise it's a pretty simple replacement.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 5:08am UTC](https://discuss.elastic.co/t/input-files-with-dynamic-filename/42695/5 "2017-07-06T05:08:56Z")

</div>

Closed on July 6, 2017, 5:08am UTC