# How filebeat process memory mapped log files
**URL:** https://discuss.elastic.co/t/how-filebeat-process-memory-mapped-log-files/337447
**Category:** Beats
**Tags:** filebeat
**Created:** [July 3, 2023, 11:26am UTC](https://discuss.elastic.co/t/how-filebeat-process-memory-mapped-log-files/337447 "2023-07-03T11:26:17Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Aleksandr\_Borisov](https://discuss.elastic.co/u/Aleksandr_Borisov)
#### Post date: [July 3, 2023, 11:26am UTC](https://discuss.elastic.co/t/how-filebeat-process-memory-mapped-log-files/337447/1 "2023-07-03T11:26:17Z")
I have found really strange behaviour of filebeat. Filebeat stop harvesting memory mapped files. I'm using log files which has constant size. To write data to logs i'm writing just string to memory and kernel flush it upon kernel finish write dirty pages. I found observation that filebeat can't collect all data from such kind of files. Filebeat skips a lot of lines in general it collect about 70% of content. Any ideas how it can be improved?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 31, 2023, 1:27pm UTC](https://discuss.elastic.co/t/how-filebeat-process-memory-mapped-log-files/337447/2 "2023-07-31T13:27:13Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.