{"action":"closed","issue":{"url":"https://api.github.com/repos/logstash-plugins/logstash-input-rabbitmq/issues/9","labels_url":"https://api.github.com/repos/logstash-plugins/logstash-input-rabbitmq/issues/9/labels{/name}","comments_url":"https://api.github.com/repos/logstash-plugins/logstash-input-rabbitmq/issues/9/comments","events_url":"https://api.github.com/repos/logstash-plugins/logstash-input-rabbitmq/issues/9/events","html_url":"https://github.com/logstash-plugins/logstash-input-rabbitmq/issues/9","id":55310629,"number":9,"title":"Feature request: Heartbeat for RabbitMQ","user":{"login":"untergeek","id":1020383,"avatar_url":"https://avatars.githubusercontent.com/u/1020383?v=3","gravatar_id":"","url":"https://api.github.com/users/untergeek","html_url":"https://github.com/untergeek","followers_url":"https://api.github.com/users/untergeek/followers","following_url":"https://api.github.com/users/untergeek/following{/other_user}","gists_url":"https://api.github.com/users/untergeek/gists{/gist_id}","starred_url":"https://api.github.com/users/untergeek/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/untergeek/subscriptions","organizations_url":"https://api.github.com/users/untergeek/orgs","repos_url":"https://api.github.com/users/untergeek/repos","events_url":"https://api.github.com/users/untergeek/events{/privacy}","received_events_url":"https://api.github.com/users/untergeek/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/logstash-plugins/logstash-input-rabbitmq/labels/enhancement","name":"enhancement","color":"009800"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-01-23T17:48:06Z","updated_at":"2015-11-04T17:13:50Z","closed_at":"2015-11-04T17:13:50Z","body":"I've noticed that our ELB is killing the Logstash connections when there's nothing moving in any direction. I've also found a guy with the same issue on HAproxy (https://groups.google.com/forum/#!topic/logstash-users/odP7k8dhinI).\r\n\r\nLogstash reconnects after a few seconds, and it seems to work when there's a ton of logs to parse, but it should have a customizable heartbeat instead, so I can set it on 20s and ELB will assume that the connection don't need to be dropped and it will be seamless without log barfing when the connection is lost...\r\n\r\n```json\r\n{:timestamp=>\"2014-06-23T16:03:34.446000+0000\", :message=>\"RabbitMQ connection error: . Will reconnect in 10 seconds...\", :level=>:error}\r\n{:timestamp=>\"2014-06-23T16:03:47.476000+0000\", :message=>\"RabbitMQ connection error: . Will reconnect in 10 seconds...\", :level=>:error}\r\n{:timestamp=>\"2014-06-23T16:04:00.502000+0000\", :message=>\"RabbitMQ connection error: . Will reconnect in 10 seconds...\", :level=>:error}\r\n{:timestamp=>\"2014-06-23T16:04:13.566000+0000\", :message=>\"RabbitMQ connection error: . Will reconnect in 10 seconds...\", :level=>:error}\r\n{:timestamp=>\"2014-06-23T16:04:26.607000+0000\", :message=>\"RabbitMQ connection error: . Will reconnect in 10 seconds...\", :level=>:error}\r\n{:timestamp=>\"2014-06-23T16:04:39.643000+0000\", :message=>\"RabbitMQ connection error: . Will reconnect in 10 seconds...\", :level=>:error}\r\n{:timestamp=>\"2014-06-23T16:04:52.662000+0000\", :message=>\"RabbitMQ connection error: . Will reconnect in 10 seconds...\", :level=>:error}\r\n{:timestamp=>\"2014-06-23T16:05:05.703000+0000\", :message=>\"RabbitMQ connection error: . Will reconnect in 10 seconds...\", :level=>:error}\r\n```\r\n\r\n(migrated from https://github.com/elasticsearch/logstash/issues/1466)"}}