# Monitoring Filebeat with the new Stats api in 6.0+

**URL:** <https://discuss.elastic.co/t/monitoring-filebeat-with-the-new-stats-api-in-6-0/125328>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [March 23, 2018, 8:34am UTC](https://discuss.elastic.co/t/monitoring-filebeat-with-the-new-stats-api-in-6-0/125328 "2018-03-23T08:34:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sarfaraz\_Ahmad](https://avatars.discourse-cdn.com/v4/letter/s/67e7ee/32.png) [@Sarfaraz\_Ahmad](https://discuss.elastic.co/u/Sarfaraz_Ahmad)\
**Post date:** [March 23, 2018, 8:34am UTC](https://discuss.elastic.co/t/monitoring-filebeat-with-the-new-stats-api-in-6-0/125328/1 "2018-03-23T08:34:29Z")

</div>

Hi,

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.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 20, 2018, 8:34am UTC](https://discuss.elastic.co/t/monitoring-filebeat-with-the-new-stats-api-in-6-0/125328/2 "2018-04-20T08:34:33Z")

</div>

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