# Any plan for HTTP input support?

**URL:** <https://discuss.elastic.co/t/any-plan-for-http-input-support/173088>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [March 20, 2019, 7:23am UTC](https://discuss.elastic.co/t/any-plan-for-http-input-support/173088 "2019-03-20T07:23:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Garlandal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/garlandal/32/42397_2.png) [@Garlandal](https://discuss.elastic.co/u/Garlandal)\
**Post date:** [March 20, 2019, 7:23am UTC](https://discuss.elastic.co/t/any-plan-for-http-input-support/173088/1 "2019-03-20T07:23:33Z")

</div>

hey, i'm using filebeat building my log server, but on the [filebeat input](https://www.elastic.co/guide/en/beats/filebeat/current/configuration-filebeat-options.html) support list, there is not HTTP input support, since [logstash](https://www.elastic.co/guide/en/logstash/6.6/plugins-inputs-http.html) and [fluentd](https://docs.fluentd.org/v1.0/articles/in_http) both have http input plugin, so is there any plan for HTTP input support or what is the best practice to build my own input plugin for filebeat?

---

<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:** [April 17, 2019, 7:23am UTC](https://discuss.elastic.co/t/any-plan-for-http-input-support/173088/2 "2019-04-17T07:23:34Z")

</div>

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