Hi, I have filebeat running on 10 hosts that send logs to a central logstash. I notice these messages on all of them. The time on different hosts does not coincide suggesting there is no specific window for these failures. 2017-12-20T05:30:57+05:30 ERR Failed to publish events caused by: read tcp…

Could filebeat be dropping messages here?

system (system) Closed January 10, 2018, 1:31pm 3

This topic was automatically closed after 21 days. New replies are no longer allowed.

Topic		Replies	Views
Filebeat failed to publish events Beats filebeat	1	527	January 12, 2022
Error on filebeat -ERR Failed to publish events caused by: read tcp Beats filebeat	6	7822	July 17, 2017
Filebeat log fails to publish events Beats filebeat	10	4818	March 1, 2023
Filebeat logging - ERROR [logstash] logstash/async.go:280 Failed to publish events caused by: read tcp Beats filebeat	3	1932	April 2, 2021
ERR Failed to publish events caused by: read tcp (filebeat Version: 5.5.1) Beats filebeat	5	4951	November 13, 2017