# Winlogbeats

**URL:** <https://discuss.elastic.co/t/winlogbeats/42120>\
**Category:** Beats\
**Created:** [February 18, 2016, 10:01am UTC](https://discuss.elastic.co/t/winlogbeats/42120 "2016-02-18T10:01:54Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![gringo](https://avatars.discourse-cdn.com/v4/letter/g/f19dbf/32.png) [@gringo](https://discuss.elastic.co/u/gringo)\
**Post date:** [February 18, 2016, 10:01am UTC](https://discuss.elastic.co/t/winlogbeats/42120/1 "2016-02-18T10:01:54Z")

</div>

I am concern with the winlogbeats sending information in the uncompressed form. Is there a way to set it to apply compression for sending information to elastic search?

---

<div class="post-metadata">

**Author:** ![tudor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tudor/32/3753_2.png) [@tudor](https://discuss.elastic.co/u/tudor)\
**Post date:** [February 18, 2016, 3:32pm UTC](https://discuss.elastic.co/t/winlogbeats/42120/2 "2016-02-18T15:32:28Z")

</div>

If you want compression, you could use Winlogbeat -\> Logstash -\> Elasticsaerch. The Logstash output in Beats supports compression.

---

<div class="post-metadata">

**Author:** ![gringo](https://avatars.discourse-cdn.com/v4/letter/g/f19dbf/32.png) [@gringo](https://discuss.elastic.co/u/gringo)\
**Post date:** [February 19, 2016, 12:44am UTC](https://discuss.elastic.co/t/winlogbeats/42120/3 "2016-02-19T00:44:10Z")

</div>

Thank you for your reply.

Just a clarification, is logstash output part of winlogbeat? Can I ensure that the winlogbeat client can send out information that is already compressed?

---

<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/winlogbeats/42120/4 "2017-07-05T21:55:33Z")

</div>