# Filebeat :- Failed to publish events caused by: client is not connected

**URL:** <https://discuss.elastic.co/t/filebeat-failed-to-publish-events-caused-by-client-is-not-connected/217603>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [February 3, 2020, 10:16am UTC](https://discuss.elastic.co/t/filebeat-failed-to-publish-events-caused-by-client-is-not-connected/217603 "2020-02-03T10:16:05Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![ragur](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ragur/32/115893_2.png) [@ragur](https://discuss.elastic.co/u/ragur)\
**Post date:** [February 6, 2020, 4:10am UTC](https://discuss.elastic.co/t/filebeat-failed-to-publish-events-caused-by-client-is-not-connected/217603/3 "2020-02-06T04:10:20Z")

</div>

Hi,  
This was happening when filebeat writing to logstash. I had to introduce kafka in between filebeat and logstash and this seems to works fine. Had to look into this when filebeat writes to logstash.

---

_[View the full topic](https://discuss.elastic.co/t/filebeat-failed-to-publish-events-caused-by-client-is-not-connected/217603)._