# Beats output to Logstash over HTTP?

**URL:** <https://discuss.elastic.co/t/beats-output-to-logstash-over-http/42185>\
**Category:** Beats\
**Created:** [February 18, 2016, 7:35pm UTC](https://discuss.elastic.co/t/beats-output-to-logstash-over-http/42185 "2016-02-18T19:35:23Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![plonka2000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/plonka2000/32/5077_2.png) [@plonka2000](https://discuss.elastic.co/u/plonka2000)\
**Post date:** [February 18, 2016, 7:35pm UTC](https://discuss.elastic.co/t/beats-output-to-logstash-over-http/42185/1 "2016-02-18T19:35:23Z")

</div>

Hi,

I've been looking around to find a way to ship events from various `libbeat` applications to Logstash, but I need to do it over HTTP using basic authentication.

I have seen that `libbeat` is able to ship to Elasticsearch using this method, but I am trying to do so for Logstash.

I have seen that Logstash has a plugin for http input, but I am unaware if this would work with any `libbeat` application, and there is no reference of it anywhere.

**Note: I am not asking for HTTPS or any SSL, only HTTP with basic authentication**

Is it possible to somehow use the libbeat 'elasticsearch' http-based output with Logstash http input?

Does anyone have any experience with this?

Thanks for any advice.

**PS: I've seen [this](https://discuss.elastic.co/t/http-output-to-logstash/33269) thread, but it seems to be asking specifically about HTTPS authentication, using SSL.**

---

<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:** [February 18, 2016, 9:10pm UTC](https://discuss.elastic.co/t/beats-output-to-logstash-over-http/42185/2 "2016-02-18T21:10:44Z")

</div>

beats-\>logstash is based on a custom protocol on plain TCP connection.

Never tried to hijack elasticsearch output in order to send to logstash. Problem is the output uses the elasticsearch bulk-API which logstash might have problems with.

---

<div class="post-metadata">

**Author:** ![plonka2000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/plonka2000/32/5077_2.png) [@plonka2000](https://discuss.elastic.co/u/plonka2000)\
**Post date:** [February 19, 2016, 1:40pm UTC](https://discuss.elastic.co/t/beats-output-to-logstash-over-http/42185/3 "2016-02-19T13:40:03Z")

</div>

Thanks very much,

From research, it seems like this might either be one of a few limited options:

1. use `elasticsearch` output in beats to use http with basic authentication.
2. use `logstash` output with TLS (requires setup of certs and/or CA).
3. submit an `enhancement` for `libbeat` http output to the elastic/beats repository and see if it can be added.

Does anyone see anything missing?

Thanks.

---

<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:** [July 5, 2017, 9:55pm UTC](https://discuss.elastic.co/t/beats-output-to-logstash-over-http/42185/4 "2017-07-05T21:55:31Z")

</div>