# ES ingest node vs logstash compression?

**URL:** <https://discuss.elastic.co/t/es-ingest-node-vs-logstash-compression/62675>\
**Category:** Elasticsearch\
**Created:** [October 11, 2016, 12:32am UTC](https://discuss.elastic.co/t/es-ingest-node-vs-logstash-compression/62675 "2016-10-11T00:32:12Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![cbuescher](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cbuescher/32/60402_2.png) [@cbuescher](https://discuss.elastic.co/u/cbuescher)\
**Post date:** [October 11, 2016, 2:00pm UTC](https://discuss.elastic.co/t/es-ingest-node-vs-logstash-compression/62675/2 "2016-10-11T14:00:04Z")

</div>

Hi,

it looks like beats just added the ability to enable gzip compression of JSON payload in this pull request:

> <https://github.com/elastic/beats/pull/1835>

This should be included in the upcoming 5.0 release then. It also seems you need to enable http compression on the ES side by setting the "[http.compression](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-http.html)" parameter on all you nodes, and this [thread](https://discuss.elastic.co/t/is-it-possible-to-send-gzip-compressed-requests-to-es/10859) also suggests your response might be compressed in that case. Some things to try out, but at least this seems to be possible somehow in the neat future.

---

_[View the full topic](https://discuss.elastic.co/t/es-ingest-node-vs-logstash-compression/62675)._