# Processing gzipped Log Files with Elastic Agent Custom Log Integration?

**URL:** <https://discuss.elastic.co/t/processing-gzipped-log-files-with-elastic-agent-custom-log-integration/290831>\
**Category:** Beats\
**Tags:** elastic-agent\
**Created:** [December 2, 2021, 9:14pm UTC](https://discuss.elastic.co/t/processing-gzipped-log-files-with-elastic-agent-custom-log-integration/290831 "2021-12-02T21:14:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![abolan](https://avatars.discourse-cdn.com/v4/letter/a/b3f665/32.png) [@abolan](https://discuss.elastic.co/u/abolan)\
**Post date:** [December 2, 2021, 9:14pm UTC](https://discuss.elastic.co/t/processing-gzipped-log-files-with-elastic-agent-custom-log-integration/290831/1 "2021-12-02T21:14:03Z")

</div>

Hello,

I have an Elastic Cloud environment set up and I'm trying to ingest and parse a number of gzipped log files from a pair of central log repository servers. The Elastic Agent is already installed and communicating without issues. I've tried using the Custom Log integration and I can pull over other log files from specified directories without issue. However, the gzipped data just shows up as a mess of Unicode characters since nothing is currently configured to process it.

I've looked into Ingest Node Pipelines and Logstash Pipelines, but neither seems like it will do exactly what I need here with the Elastic Agent. Is unzipping and ingesting this data currently supported through the Elastic Agent somehow, or do I need to pursue another route to make this work?

Thank you!

---

<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:** [December 30, 2021, 11:14pm UTC](https://discuss.elastic.co/t/processing-gzipped-log-files-with-elastic-agent-custom-log-integration/290831/2 "2021-12-30T23:14:26Z")

</div>

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