# File beat - handle too big registry file

**URL:** <https://discuss.elastic.co/t/file-beat-handle-too-big-registry-file/340719>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [August 14, 2023, 8:10am UTC](https://discuss.elastic.co/t/file-beat-handle-too-big-registry-file/340719 "2023-08-14T08:10:38Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![sean\_kotler](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sean_kotler/32/122802_2.png) [@sean\_kotler](https://discuss.elastic.co/u/sean_kotler)\
**Post date:** [August 14, 2023, 8:10am UTC](https://discuss.elastic.co/t/file-beat-handle-too-big-registry-file/340719/1 "2023-08-14T08:10:38Z")

</div>

Hi Team,  
I would like to understand how to handle filebeat too big registry file when logs files needs to be process only **once** (old logs(logs that are already in my logs folder, before my filebeat service will be in use) and new logs) **no new lines will be written to file once he arrives in my logs folder**.  
I thought about one time solution of create for once the service without ignore\_older and clean\_inactive, let all the old logs to be processed with filebeat, disable the service and create it again with ignore\_older and clean\_inactive.  
There are an alternative? or maybe I just don't understand filebeat well?

Thanks,  
Sean Kotler

---

<div class="post-metadata">

**Author:** ![sean\_kotler](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sean_kotler/32/122802_2.png) [@sean\_kotler](https://discuss.elastic.co/u/sean_kotler)\
**Post date:** [August 20, 2023, 7:59am UTC](https://discuss.elastic.co/t/file-beat-handle-too-big-registry-file/340719/2 "2023-08-20T07:59:43Z")

</div>

Any ideas?

---

<div class="post-metadata">

**Author:** ![Rios](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rios/32/95745_2.png) [@Rios](https://discuss.elastic.co/u/Rios)\
**Post date:** [August 20, 2023, 8:14pm UTC](https://discuss.elastic.co/t/file-beat-handle-too-big-registry-file/340719/3 "2023-08-20T20:14:46Z")

</div>

What are settings in filebeat.yml for:

- `ignore_older`
- `clean_inactive`
- `scan_frequency`

Have you read [this](https://www.elastic.co/guide/en/beats/filebeat/current/reduce-registry-size.html)?

---

<div class="post-metadata">

**Author:** ![sean\_kotler](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sean_kotler/32/122802_2.png) [@sean\_kotler](https://discuss.elastic.co/u/sean_kotler)\
**Post date:** [August 22, 2023, 11:06am UTC](https://discuss.elastic.co/t/file-beat-handle-too-big-registry-file/340719/4 "2023-08-22T11:06:27Z")

</div>

Yes I do,  
my problem is that I have old logs files that also needs to be process at the first run.  
So if I will set ignore\_older the log files wont be processed

---

<div class="post-metadata">

**Author:** ![Rios](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rios/32/95745_2.png) [@Rios](https://discuss.elastic.co/u/Rios)\
**Post date:** [August 22, 2023, 8:32pm UTC](https://discuss.elastic.co/t/file-beat-handle-too-big-registry-file/340719/5 "2023-08-22T20:32:53Z")

</div>

Well if FB read logs older than X days/hours, no need to send again to ES.  
Try to find your answer [here](https://github.com/elastic/beats/issues/1600), there is more details.

---

<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:** [September 19, 2023, 10:33pm UTC](https://discuss.elastic.co/t/file-beat-handle-too-big-registry-file/340719/6 "2023-09-19T22:33:13Z")

</div>

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