Winlogbeat - Footprint as a shipper?

Hi All,

I have a question where I would like to know the footprint (resource usage) when Winlogbeat is operating on a Windows Server when collecting and shipping logs.

Also I would like to know as to what would happen if Winlogbeat is unable to connect with Logstash/Elasticsearch. Will it keep the log queue piling up eating resources or will the service stop after a set timeout period (default 90s)?

Thanks in advance!

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