# Should I add a output plugin named "tcp" into libbeats?

**URL:** <https://discuss.elastic.co/t/should-i-add-a-output-plugin-named-tcp-into-libbeats/88404>\
**Category:** Beats\
**Created:** [June 6, 2017, 11:02am UTC](https://discuss.elastic.co/t/should-i-add-a-output-plugin-named-tcp-into-libbeats/88404 "2017-06-06T11:02:31Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![dongmx](https://avatars.discourse-cdn.com/v4/letter/d/49beb7/32.png) [@dongmx](https://discuss.elastic.co/u/dongmx)\
**Post date:** [June 6, 2017, 11:02am UTC](https://discuss.elastic.co/t/should-i-add-a-output-plugin-named-tcp-into-libbeats/88404/1 "2017-06-06T11:02:31Z")

</div>

I implemented an output plugin named "tcp" with beats 6.0.0alpha. It just looks like logstash "tcp" output plugin. Write events over a TCP socket. Each event json is separated by a newline.Connect to a server to push event. Users can config codec with "json" or "format string".

It's useful for me. Cause I don't want to transform messages by logstash, it's not fast enough for me.

I wonder if my work about this is useful for others ?

---

<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:** [June 7, 2017, 10:09am UTC](https://discuss.elastic.co/t/should-i-add-a-output-plugin-named-tcp-into-libbeats/88404/2 "2017-06-07T10:09:16Z")

</div>

We are not too keen to add new outputs to beats right now.

But as the output is useful for you and maybe others, we generally recommend the approach taken by [beats-output-http](https://github.com/raboof/beats-output-http).

Alternatively you can try to turn your output into a go plugin (but plugins in go are somewhat tricky and we normally have plugins not enabled in our release builds). You can find some sample plugins here: [https://github.com/urso/beats-sample-plugins](https://github.com/urso/beats-sample-plugins)

---

<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:** [June 7, 2017, 10:11am UTC](https://discuss.elastic.co/t/should-i-add-a-output-plugin-named-tcp-into-libbeats/88404/3 "2017-06-07T10:11:14Z")

</div>

Currently we maintain a list of community beats [https://www.elastic.co/guide/en/beats/libbeat/current/community-beats.html](https://www.elastic.co/guide/en/beats/libbeat/current/community-beats.html) in our docs. The beats-output-http is not listed yet, but with more outputs being added, we might start to list them as well.

---

<div class="post-metadata">

**Author:** ![dongmx](https://avatars.discourse-cdn.com/v4/letter/d/49beb7/32.png) [@dongmx](https://discuss.elastic.co/u/dongmx)\
**Post date:** [June 8, 2017, 1:52am UTC](https://discuss.elastic.co/t/should-i-add-a-output-plugin-named-tcp-into-libbeats/88404/4 "2017-06-08T01:52:44Z")

</div>

Thanks for your reply. beats-output-http looks good, I'll have a try. I also will maintain my repo in my github, after all TCP is different from HTTP. HTTP headers are useless in my scenario, TCP can save so much traffic.

---

<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:** [June 27, 2017, 11:03am UTC](https://discuss.elastic.co/t/should-i-add-a-output-plugin-named-tcp-into-libbeats/88404/5 "2017-06-27T11:03:02Z")

</div>

This topic was automatically closed after 21 days. New replies are no longer allowed.