Failed to publish events

Elastic Stack Beats
1

Hi All,

We see the following error in filebeat log resulting in loss of data:

pipeline/output.go:121  Failed to publish events: write tcp 19.14.25.26:42660->14.18.8.1:5044: write: connection reset by peer

It seems that filebeat is not able to push messages to the remote Logstash listening on port 5044.

This error is seen on numerous filebeat logs which makes me believe that the issue is on the Logstash side.

Question: What are the tuning parameters required for both Logstash and OS (RHEL 7) as I believe Logstash is getting swamped with messages?

2

Is this the recommended approach?

3

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