# RelayBeat

**URL:** <https://discuss.elastic.co/t/relaybeat/81382>\
**Category:** Beats\
**Created:** [April 5, 2017, 11:05pm UTC](https://discuss.elastic.co/t/relaybeat/81382 "2017-04-05T23:05:45Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rswestmoreland](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rswestmoreland/32/17476_2.png) [@rswestmoreland](https://discuss.elastic.co/u/rswestmoreland)\
**Post date:** [April 5, 2017, 11:05pm UTC](https://discuss.elastic.co/t/relaybeat/81382/1 "2017-04-05T23:05:45Z")

</div>

Hello,

Right now I have various Beats connecting to a Graylog Input (configured the same way you would connect it to Logstash). This works really well, but what I'd prefer to do is have another Beat on the other end of the connection, with similar options _including_ writing to disk. My goal are these 2 scenarios:

Disk -\> Beat[a1] ----\> Beat[b1] -\> Disk

Disk -\> Beat[a1] -----\> Beat[b1] ----\> Beat[c3] ---\> Beat[d7] -\> Elasticsearch

So the Beats are either an efficient way to move log data from one server to another, so you can do stuff to the data on the other end before loading it into ES/LS/GL, or the Beats can be setup in a load balancing tree for a really large distributed setup.

I know I can accomplish this with logstash, but I prefer how lightweight go-based Beats are, and trying to avoid anything Ruby related in my stack.

Anybody else think about creating a similar Beat? Does something like this already exist, maybe a POC Beat someone was working on? If I wanted to find someone to help me build this, where do I start?

thanks!

---

<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:** [April 6, 2017, 6:07am UTC](https://discuss.elastic.co/t/relaybeat/81382/2 "2017-04-06T06:07:45Z")

</div>

I'm only aware of this project: [https://github.com/logmatic/beats-forwarder](https://github.com/logmatic/beats-forwarder)

It uses the [go-based lumberjack client/server libs](https://github.com/elastic/go-lumber). e.g. see [test lumberjack server](https://github.com/elastic/go-lumber/tree/master/cmd/tst-lj).

---

<div class="post-metadata">

**Author:** ![rswestmoreland](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rswestmoreland/32/17476_2.png) [@rswestmoreland](https://discuss.elastic.co/u/rswestmoreland)\
**Post date:** [April 6, 2017, 12:15pm UTC](https://discuss.elastic.co/t/relaybeat/81382/3 "2017-04-06T12:15:18Z")

</div>

Thanks, that's pretty close! I'll test it out.

---

<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:** [April 7, 2017, 10:49am UTC](https://discuss.elastic.co/t/relaybeat/81382/4 "2017-04-07T10:49:33Z")

</div>

It should be quite easy to build a custom beat using go-lumber 😉

---

<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 26, 2017, 11:06pm UTC](https://discuss.elastic.co/t/relaybeat/81382/5 "2017-04-26T23:06:12Z")

</div>

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