# Feed HTTP response body to Elasticsearch

**URL:** <https://discuss.elastic.co/t/feed-http-response-body-to-elasticsearch/92288>\
**Category:** Beats\
**Tags:** heartbeat\
**Created:** [July 7, 2017, 2:42pm UTC](https://discuss.elastic.co/t/feed-http-response-body-to-elasticsearch/92288 "2017-07-07T14:42:23Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![owulff](https://avatars.discourse-cdn.com/v4/letter/o/f475e1/32.png) [@owulff](https://discuss.elastic.co/u/owulff)\
**Post date:** [July 7, 2017, 2:42pm UTC](https://discuss.elastic.co/t/feed-http-response-body-to-elasticsearch/92288/1 "2017-07-07T14:42:23Z")

</div>

Hi there

Is it planned to support sending the http response body to Elasticsearch if it is in JSON format?

Thanks  
Oli

---

<div class="post-metadata">

**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\
**Post date:** [July 7, 2017, 3:06pm UTC](https://discuss.elastic.co/t/feed-http-response-body-to-elasticsearch/92288/2 "2017-07-07T15:06:48Z")

</div>

Seems not to be on the agenda. Check out open heartbeat issues and enhancement requests: [https://github.com/elastic/beats/issues?q=is%3Aopen+is%3Aissue+label%3AHeartbeat](https://github.com/elastic/beats/issues?q=is%3Aopen+is%3Aissue+label%3AHeartbeat)

Purpose of heartbeat is to check a service is available. What's you use-case in reporting the body response?

---

<div class="post-metadata">

**Author:** ![owulff](https://avatars.discourse-cdn.com/v4/letter/o/f475e1/32.png) [@owulff](https://discuss.elastic.co/u/owulff)\
**Post date:** [July 7, 2017, 3:17pm UTC](https://discuss.elastic.co/t/feed-http-response-body-to-elasticsearch/92288/3 "2017-07-07T15:17:51Z")

</div>

At the moment I just wanted to feed the logstash management stats into elasticsearch because we run 2.3 of ES at the moment.

I know there is the http module of metricbeat at some stage. In general, there is some overlap with watcher and what you can do in heartbeat. IMHO, watcher is much more powerfull for the conditions and therefore I just wanted to feed the response into ES. Especially you can manage the conditions over REST whereas in heartbeat, you must configure it in a local configuration file.

---

<div class="post-metadata">

**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\
**Post date:** [July 7, 2017, 3:41pm UTC](https://discuss.elastic.co/t/feed-http-response-body-to-elasticsearch/92288/4 "2017-07-07T15:41:25Z")

</div>

Have you considered the logstash [http\_poller module](https://www.elastic.co/guide/en/logstash/current/plugins-inputs-http_poller.html)?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [August 4, 2017, 3:41pm UTC](https://discuss.elastic.co/t/feed-http-response-body-to-elasticsearch/92288/5 "2017-08-04T15:41:35Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.