Clark Boylan 749ee5405c Timeout logstash es pushes after 300s ... By default the elasticsearch output plugin for logstash has no timeout. I think this is the cause of logstash daemons hanging when we have elasticsearch node outages. Goal here is to have the timeout force the request to be retried again (ideally against a different server entirely but even if it is simply retried to the same server we should operate properly again once the server that went down is back up). Change-Id: I0511f32f8ee3f0c40987cab3e2528a85595785b2		2017-12-08 13:48:43 -08:00
..
agent.conf.erb	Better multiline handling for Jenkins console logs	2013-04-11 21:07:58 +00:00
indexer.conf.erb	Handle journald timestamps in multiline logstash	2017-05-03 08:34:04 -07:00
input.conf.erb	Use logstash filters from filters repo	2016-04-26 15:33:03 -07:00
jenkins-log-worker.yaml.erb	Revert "Disable crm114 on the logstash worker nodes"	2017-11-29 10:21:43 -08:00
jenkins-subunit-worker.yaml.erb	Fix use of _ that should be - in mqtt-ca_certs	2017-04-26 13:53:49 -07:00
output.conf.erb	Timeout logstash es pushes after 300s	2017-12-08 13:48:43 -08:00
redis-output.conf.erb	Add skeleton logstash module.	2013-01-29 20:44:09 +00:00