# Sending a record to multiple host. IE Teeing the data

**URL:** https://discuss.elastic.co/t/sending-a-record-to-multiple-host-ie-teeing-the-data/80532
**Category:** Beats
**Tags:** filebeat
**Created:** [March 29, 2017, 6:28pm UTC](https://discuss.elastic.co/t/sending-a-record-to-multiple-host-ie-teeing-the-data/80532 "2017-03-29T18:28:22Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Jeremy\_Foran](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jeremy_foran/32/15434_2.png) [@Jeremy\_Foran](https://discuss.elastic.co/u/Jeremy_Foran)
#### Post date: [March 29, 2017, 6:28pm UTC](https://discuss.elastic.co/t/sending-a-record-to-multiple-host-ie-teeing-the-data/80532/1 "2017-03-29T18:28:22Z")

</div>

I would like to configure my filebeats to deliver each record to two different hosts. In other words, a have multiple clusters and I would like to have log data delivered to both. What is the appropriate approach?

The use case is that I am going from 2.x to 5.x by standing up a new cluster in parallel and I want to test the new cluster before cutting over.

---

<div class="post-metadata">

### Author: ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [March 30, 2017, 1:03am UTC](https://discuss.elastic.co/t/sending-a-record-to-multiple-host-ie-teeing-the-data/80532/2 "2017-03-30T01:03:21Z")

</div>

You will need to use Logstash or Kafka + LS to do that, beats only support a single output destination.

---

<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: [March 30, 2017, 8:30am UTC](https://discuss.elastic.co/t/sending-a-record-to-multiple-host-ie-teeing-the-data/80532/3 "2017-03-30T08:30:27Z")

</div>

Beats on purpose does not support event duplication, as this would create some indirect coupling between the 2 systems (back-pressure from system 1 will affect system 2). Using `beats->kafka` can be used to decouple the target systems, as you can use distinct `consumer groups` to read the events from kafka into the target system. Don't have LS output the events to both hosts (will couple the target systems again), but one LS instance/pipeline per target host. E.g. having one system for production and a second for development, you don't want the dev environment (potentially being down) affect the production environment.

---

<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 27, 2017, 8:30am UTC](https://discuss.elastic.co/t/sending-a-record-to-multiple-host-ie-teeing-the-data/80532/4 "2017-04-27T08:30:41Z")

</div>

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