Lower Filebeat memory usage


I'm trying to give Filebeat as little memory as possible. My main issue is that I have a ton of independent containers on a VM and sometimes (due to network issues) Filebeat can't forward all the logs. However, after the issue is solved all (hundreds) Filebeat instances are throwing data to memory like crazy and that brings down the VM itself. I tried to use disk queue, but it didn't have any effect on the memory usage. I'm monitoring the memory usage with Metricbeat.

Do you have any suggestions limiting Filebeat's memory usage? Or what am I missing when I add the disk queue to the configuration?

Filebeat version: 7.11.0


Hearing that many crickets chirping, I think that since the function is in beta it doesn't really lower memory consumption (of course, the docs never stated that) but stores events on disk for persistency.

Is there any way to limit the maximum memory usage of a Filebeat process without changing the number of events stored in memory?

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