When enabling the audit log parsing with the elasticsearch module for filbeat, the audit logs are not rotate correctly because filebeat keeps the files open. That also causes the disk to get full quickly because of the amount of audit logs.
Is there a way to keep using the module without this issues?
The issue is not coming from using the module. The root cause is that the output is processing the events from Filebeat too slowly. Do you have any errors in the logs of the output?
Also, you can set the appropiate close_* option, so Filebeat closes files: https://www.elastic.co/guide/en/beats/filebeat/6.2/configuration-filebeat-options.html#close-options
As you are using a module, you need to set it under input:
I've enabled close_removed but the issue is not fixed. Also the issue is with the audit part, not server. All the others work correctly, but there's not as many logs as the audit.
I've tried searching for any errors, but I cannot see any. The output is elasticsearch itself, so maybe there's a loop issue?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.