From e8966f4568f01f107335a1bd457c4e9bdf6f5e02 Mon Sep 17 00:00:00 2001 From: Jonathan Rosser Date: Mon, 24 Sep 2018 13:28:47 +0100 Subject: [PATCH] Increase beat input inactivity timeout This defaults to 60s, and there is a constant background of errors making noise in the logs of the form: ERROR pipeline/output.go:121 Failed to publish events: write tcp 10.11.3.128:40770->10.11.128.94:5044: write: connection reset by peer Advice seems to be to increase client_inactivity_timout [1]. Tested in one environment and the log noise is gone. [1] https://discuss.elastic.co/t/solved-filebeat-logstash-connection-reset-by-peer/87012 Change-Id: Ia93867826a0c32192e3c37ea101f9a95a29e3d00 --- elk_metrics_6x/templates/logstash-pipelines.yml.j2 | 1 + 1 file changed, 1 insertion(+) diff --git a/elk_metrics_6x/templates/logstash-pipelines.yml.j2 b/elk_metrics_6x/templates/logstash-pipelines.yml.j2 index b10f07d8..da6ca200 100644 --- a/elk_metrics_6x/templates/logstash-pipelines.yml.j2 +++ b/elk_metrics_6x/templates/logstash-pipelines.yml.j2 @@ -8,6 +8,7 @@ input { beats { id => "inputBeats" + client_inactivity_timeout => 300 port => {{ logstash_beat_input_port }} add_field => { "[@metadata][source_type]" => "beats"