{"action":"created","issue":{"url":"https://api.github.com/repos/logstash-plugins/logstash-output-elasticsearch/issues/219","labels_url":"https://api.github.com/repos/logstash-plugins/logstash-output-elasticsearch/issues/219/labels{/name}","comments_url":"https://api.github.com/repos/logstash-plugins/logstash-output-elasticsearch/issues/219/comments","events_url":"https://api.github.com/repos/logstash-plugins/logstash-output-elasticsearch/issues/219/events","html_url":"https://github.com/logstash-plugins/logstash-output-elasticsearch/issues/219","id":99501148,"number":219,"title":"Better User Experience When Elasticsearch is Down","user":{"login":"andrewvc","id":131427,"avatar_url":"https://avatars.githubusercontent.com/u/131427?v=3","gravatar_id":"","url":"https://api.github.com/users/andrewvc","html_url":"https://github.com/andrewvc","followers_url":"https://api.github.com/users/andrewvc/followers","following_url":"https://api.github.com/users/andrewvc/following{/other_user}","gists_url":"https://api.github.com/users/andrewvc/gists{/gist_id}","starred_url":"https://api.github.com/users/andrewvc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/andrewvc/subscriptions","organizations_url":"https://api.github.com/users/andrewvc/orgs","repos_url":"https://api.github.com/users/andrewvc/repos","events_url":"https://api.github.com/users/andrewvc/events{/privacy}","received_events_url":"https://api.github.com/users/andrewvc/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2015-08-06T18:50:30Z","updated_at":"2015-08-06T18:58:29Z","closed_at":null,"body":"Currently if elasticsearch dies weird errors can occur. We should perform some sort of sniffing to check if ES is up, and report it ASAP to the user in a very noticeable way. This was moved from this thread: https://github.com/logstash-plugins/logstash-output-elasticsearch/issues/141#issuecomment-127418528"},"comment":{"url":"https://api.github.com/repos/logstash-plugins/logstash-output-elasticsearch/issues/comments/128474137","html_url":"https://github.com/logstash-plugins/logstash-output-elasticsearch/issues/219#issuecomment-128474137","issue_url":"https://api.github.com/repos/logstash-plugins/logstash-output-elasticsearch/issues/219","id":128474137,"user":{"login":"jordansissel","id":131818,"avatar_url":"https://avatars.githubusercontent.com/u/131818?v=3","gravatar_id":"","url":"https://api.github.com/users/jordansissel","html_url":"https://github.com/jordansissel","followers_url":"https://api.github.com/users/jordansissel/followers","following_url":"https://api.github.com/users/jordansissel/following{/other_user}","gists_url":"https://api.github.com/users/jordansissel/gists{/gist_id}","starred_url":"https://api.github.com/users/jordansissel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jordansissel/subscriptions","organizations_url":"https://api.github.com/users/jordansissel/orgs","repos_url":"https://api.github.com/users/jordansissel/repos","events_url":"https://api.github.com/users/jordansissel/events{/privacy}","received_events_url":"https://api.github.com/users/jordansissel/received_events","type":"User","site_admin":false},"created_at":"2015-08-06T18:58:29Z","updated_at":"2015-08-06T18:58:29Z","body":"@andrewvc for item 1; I think showing which event(s) failed and each specific failure for that event (I think the bulk response has the per-doc failure exceptions we could show to users). For item 2, having a background health check going on to check cluster health could be useful indeed to help better-inform any reports to users. +1 on both changes. I suspect we'll add more in the future, but this is a great start :)"}}