# Filestream and sequencing

**URL:** <https://discuss.elastic.co/t/filestream-and-sequencing/328809>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [March 29, 2023, 10:12am UTC](https://discuss.elastic.co/t/filestream-and-sequencing/328809 "2023-03-29T10:12:19Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![kakoni](https://avatars.discourse-cdn.com/v4/letter/k/8c91f0/32.png) [@kakoni](https://discuss.elastic.co/u/kakoni)\
**Post date:** [March 29, 2023, 10:12am UTC](https://discuss.elastic.co/t/filestream-and-sequencing/328809/1 "2023-03-29T10:12:19Z")

</div>

Hi. Lets say that I've got log directory full of old files;  
data\_20230301.log  
data\_20230402.log  
..  
data\_20230329.log  
and so on.

Is it somehow possible to configure filestream input so that these files are read/processed in sequence? (Meaning first read data\_20230301.log in sequence and then proceed to data\_20230402.log..)

---

<div class="post-metadata">

**Author:** ![kakoni](https://avatars.discourse-cdn.com/v4/letter/k/8c91f0/32.png) [@kakoni](https://discuss.elastic.co/u/kakoni)\
**Post date:** [March 29, 2023, 12:47pm UTC](https://discuss.elastic.co/t/filestream-and-sequencing/328809/2 "2023-03-29T12:47:46Z")

</div>

So I'm guessing the proper way to do is to use `harvester_limit` to 1 and play around with `close_timeout`.

Also it seems that there is a bug? with filestream and harvester\_limits so old log input works better.

---

<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:** [April 26, 2023, 2:48pm UTC](https://discuss.elastic.co/t/filestream-and-sequencing/328809/3 "2023-04-26T14:48:46Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.