{"action":"created","issue":{"url":"https://api.github.com/repos/logstash-plugins/logstash-input-http-poller/issues/7","labels_url":"https://api.github.com/repos/logstash-plugins/logstash-input-http-poller/issues/7/labels{/name}","comments_url":"https://api.github.com/repos/logstash-plugins/logstash-input-http-poller/issues/7/comments","events_url":"https://api.github.com/repos/logstash-plugins/logstash-input-http-poller/issues/7/events","html_url":"https://github.com/logstash-plugins/logstash-input-http-poller/issues/7","id":91650830,"number":7,"title":"Should response be in message as a hash ?","user":{"login":"maximede","id":2980192,"avatar_url":"https://avatars.githubusercontent.com/u/2980192?v=3","gravatar_id":"","url":"https://api.github.com/users/maximede","html_url":"https://github.com/maximede","followers_url":"https://api.github.com/users/maximede/followers","following_url":"https://api.github.com/users/maximede/following{/other_user}","gists_url":"https://api.github.com/users/maximede/gists{/gist_id}","starred_url":"https://api.github.com/users/maximede/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/maximede/subscriptions","organizations_url":"https://api.github.com/users/maximede/orgs","repos_url":"https://api.github.com/users/maximede/repos","events_url":"https://api.github.com/users/maximede/events{/privacy}","received_events_url":"https://api.github.com/users/maximede/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/logstash-plugins/logstash-input-http-poller/labels/question","name":"question","color":"cc317c"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-06-28T22:36:47Z","updated_at":"2015-06-28T22:53:49Z","closed_at":null,"body":"I disagree a bit with the new implementation regarding the decoding of the response body.\r\nWe are currently putting it completely in the message, as a hash.\r\nIt means that if you want to use the content present in the json/xml, you'll need to parse it in a filter.\r\n\r\nI think it would it make sense to provide an option to parse the content of the response and add all the variables to the event, as I was doing in the initial version of this input\r\n\r\nThought ? "},"comment":{"url":"https://api.github.com/repos/logstash-plugins/logstash-input-http-poller/issues/comments/116357108","html_url":"https://github.com/logstash-plugins/logstash-input-http-poller/issues/7#issuecomment-116357108","issue_url":"https://api.github.com/repos/logstash-plugins/logstash-input-http-poller/issues/7","id":116357108,"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},"created_at":"2015-06-28T22:53:48Z","updated_at":"2015-06-28T22:53:48Z","body":"Hi Maxime! I was mostly worried that if variables such as 'url' were part of the event itself (url is a very common key) it would be overwritten, hence the nesting. \r\n\r\nI'm definitely open to some alternative ideas here. I'd also considered flipping it around and stuffing the metadata in '_poller_metadata' or something. What are your thoughts?"}}