# Filebeat publish metrics on start up to elastic and then stops publishing metrics

**URL:** <https://discuss.elastic.co/t/filebeat-publish-metrics-on-start-up-to-elastic-and-then-stops-publishing-metrics/104742>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [October 20, 2017, 6:17pm UTC](https://discuss.elastic.co/t/filebeat-publish-metrics-on-start-up-to-elastic-and-then-stops-publishing-metrics/104742 "2017-10-20T18:17:26Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![ajstark123](https://avatars.discourse-cdn.com/v4/letter/a/73ab20/32.png) [@ajstark123](https://discuss.elastic.co/u/ajstark123)\
**Post date:** [October 20, 2017, 6:17pm UTC](https://discuss.elastic.co/t/filebeat-publish-metrics-on-start-up-to-elastic-and-then-stops-publishing-metrics/104742/1 "2017-10-20T18:17:26Z")

</div>

Filebeat publish metrics on start up to elastic and then stops publishing metrics.

We stopped filebeat by doing a kill -9 of the pid. Systemd restarts filebeat. Filebeat published data to the logs and then stops publishing

We are seeing these entries in the logs

2017-10-20T14:04:51-04:00 INFO Non-zero metrics in the last 30s: filebeat.harvester.open\_files=2 filebeat.harvester.running=2 filebeat.harvester.started=2 libbeat.es.call\_count.PublishEvents=1 libbeat.es.publish.read\_bytes=475 libbeat.es.publish.write\_bytes=29946 libbeat.publisher.published\_events=2046  
2017-10-20T14:05:21-04:00 INFO No non-zero metrics in the last 30s  
2017-10-20T14:05:21-04:00 INFO Error publishing events (retrying): temporary bulk send failure  
2017-10-20T14:05:22-04:00 INFO Connected to Elasticsearch version 5.5.2  
2017-10-20T14:05:22-04:00 INFO Trying to load template for client: [http://monatee-loggy-master-cnj.dev.bnymellon.net:80](http://monatee-loggy-master-cnj.dev.bnymellon.net:80)  
2017-10-20T14:05:22-04:00 INFO Template already exists and will not be overwritten.  
2017-10-20T14:05:51-04:00 INFO Non-zero metrics in the last 30s: libbeat.es.call\_count.PublishEvents=1 libbeat.es.publish.read\_bytes=1064 libbeat.es.publish.write\_bytes=6981 libbeat.es.published\_and\_acked\_events=39 libbeat.es.published\_but\_not\_acked\_events=11

---

<div class="post-metadata">

**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\
**Post date:** [October 23, 2017, 12:53pm UTC](https://discuss.elastic.co/t/filebeat-publish-metrics-on-start-up-to-elastic-and-then-stops-publishing-metrics/104742/2 "2017-10-23T12:53:02Z")

</div>

Which version of filebeat are you using?

---

<div class="post-metadata">

**Author:** ![ajstark123](https://avatars.discourse-cdn.com/v4/letter/a/73ab20/32.png) [@ajstark123](https://discuss.elastic.co/u/ajstark123)\
**Post date:** [October 23, 2017, 4:41pm UTC](https://discuss.elastic.co/t/filebeat-publish-metrics-on-start-up-to-elastic-and-then-stops-publishing-metrics/104742/3 "2017-10-23T16:41:58Z")

</div>

We are using 5.5.2 - filebeat-5.5.2-linux-x86\_64.tar.gz

I checked this morning and the issue resolved itself. I was seeing logs for the last 1 minute. I am surprised that it resolved itself. I was not expecting to see logs this morning

---

<div class="post-metadata">

**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\
**Post date:** [October 24, 2017, 12:09pm UTC](https://discuss.elastic.co/t/filebeat-publish-metrics-on-start-up-to-elastic-and-then-stops-publishing-metrics/104742/4 "2017-10-24T12:09:36Z")

</div>

Kind of sounds like network issues or ES cluster not being stable.

---

<div class="post-metadata">

**Author:** ![ajstark123](https://avatars.discourse-cdn.com/v4/letter/a/73ab20/32.png) [@ajstark123](https://discuss.elastic.co/u/ajstark123)\
**Post date:** [October 24, 2017, 2:25pm UTC](https://discuss.elastic.co/t/filebeat-publish-metrics-on-start-up-to-elastic-and-then-stops-publishing-metrics/104742/5 "2017-10-24T14:25:57Z")

</div>

How do we check the stability of the Elastic cliuster

---

<div class="post-metadata">

**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\
**Post date:** [October 24, 2017, 2:28pm UTC](https://discuss.elastic.co/t/filebeat-publish-metrics-on-start-up-to-elastic-and-then-stops-publishing-metrics/104742/6 "2017-10-24T14:28:56Z")

</div>

X-pack basic (free) contains some monitoring support. Also check Elasticsearch logs.

---

<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:** [November 21, 2017, 2:29pm UTC](https://discuss.elastic.co/t/filebeat-publish-metrics-on-start-up-to-elastic-and-then-stops-publishing-metrics/104742/7 "2017-11-21T14:29:16Z")

</div>

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