# Winlogbeat forward

**URL:** <https://discuss.elastic.co/t/winlogbeat-forward/128325>\
**Category:** Beats\
**Created:** [April 17, 2018, 9:32am UTC](https://discuss.elastic.co/t/winlogbeat-forward/128325 "2018-04-17T09:32:14Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Felix\_Kutscher](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/felix_kutscher/32/83575_2.png) [@Felix\_Kutscher](https://discuss.elastic.co/u/Felix_Kutscher)\
**Post date:** [April 17, 2018, 9:32am UTC](https://discuss.elastic.co/t/winlogbeat-forward/128325/1 "2018-04-17T09:32:14Z")

</div>

Hi, it is possible to send windlogbeat to logstash and then logstash send via tcp or syslog to an other logstash.

Winlogbeat --\> Logstash -tcp/syslog-\> Logstash --\> Elasticsearch

regards  
Felix

---

<div class="post-metadata">

**Author:** ![jsoriano](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsoriano/32/27920_2.png) [@jsoriano](https://discuss.elastic.co/u/jsoriano)\
**Post date:** [April 17, 2018, 12:12pm UTC](https://discuss.elastic.co/t/winlogbeat-forward/128325/2 "2018-04-17T12:12:33Z")

</div>

Yes, it is possible, you can see in the documentation [how to connect the two logstash instances](https://www.elastic.co/guide/en/logstash/current/ls-to-ls.html). But take into account that tcp output to tcp input logstash communication doesn't provide any guarantee and there can be data loss.

---

<div class="post-metadata">

**Author:** ![Felix\_Kutscher](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/felix_kutscher/32/83575_2.png) [@Felix\_Kutscher](https://discuss.elastic.co/u/Felix_Kutscher)\
**Post date:** [April 17, 2018, 12:57pm UTC](https://discuss.elastic.co/t/winlogbeat-forward/128325/3 "2018-04-17T12:57:56Z")

</div>

Thanks jsoriano. But lumperjack provide this guarantee?

---

<div class="post-metadata">

**Author:** ![jsoriano](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsoriano/32/27920_2.png) [@jsoriano](https://discuss.elastic.co/u/jsoriano)\
**Post date:** [April 17, 2018, 1:58pm UTC](https://discuss.elastic.co/t/winlogbeat-forward/128325/4 "2018-04-17T13:58:11Z")

</div>

Yes, lumberjack can be more safe for your case. Also, if it fits in your architecture, you can consider to introduce a queue between both logstash.

Just curious, why do you have two chained logstash instances?

---

<div class="post-metadata">

**Author:** ![Felix\_Kutscher](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/felix_kutscher/32/83575_2.png) [@Felix\_Kutscher](https://discuss.elastic.co/u/Felix_Kutscher)\
**Post date:** [April 18, 2018, 9:49am UTC](https://discuss.elastic.co/t/winlogbeat-forward/128325/5 "2018-04-18T09:49:58Z")

</div>

> Just curious, why do you have two chained logstash instances?  
> Because of the network architecture.

---

<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:** [May 16, 2018, 11:50am UTC](https://discuss.elastic.co/t/winlogbeat-forward/128325/6 "2018-05-16T11:50:13Z")

</div>

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