# Tuning up filebeat

**URL:** <https://discuss.elastic.co/t/tuning-up-filebeat/159708>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [December 6, 2018, 10:29am UTC](https://discuss.elastic.co/t/tuning-up-filebeat/159708 "2018-12-06T10:29:48Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [December 6, 2018, 1:52pm UTC](https://discuss.elastic.co/t/tuning-up-filebeat/159708/2 "2018-12-06T13:52:56Z")

</div>

Filebeat can be quite fast. When tuning it's a matter of tuning all services, Beats, Logstash, and Elasticsearch. Tuning needs can very much differ from environment to environment.

I'd recommend to read this [discussion](https://discuss.elastic.co/t/filebeat-slow-improve-performance/144717), as it contains a many tips and good practices applied.

---

_[View the full topic](https://discuss.elastic.co/t/tuning-up-filebeat/159708)._