Monitoring Filebeat with the new Stats api in 6.0+


I was wondering how I would go about monitoring filebeat. I need to send an email out when logs have stopped shipping.

These are my findings so far:

  1. I think the retry counted in refreshed every 90 seconds. If filebeat is not able to open a connection to the remote, changes to the retry count value will be updated after 90 seconds only.

One approach that I could think off, is to sample retry count value 3-4 times every 2 minutes.
if retry count kept on increasing in all 4 samples, that implies that filebeat is not sending any logs.

Please share your inputs on how to go about monitoring filebeat.

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