# Problem. Filebeat 7.4.0 excesive syslog size

**URL:** <https://discuss.elastic.co/t/problem-filebeat-7-4-0-excesive-syslog-size/208291>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [November 18, 2019, 10:57am UTC](https://discuss.elastic.co/t/problem-filebeat-7-4-0-excesive-syslog-size/208291 "2019-11-18T10:57:17Z")\
**Posts on this page:** 2\
**Page:** 2

<div class="post-metadata">

**Author:** ![mfries](https://avatars.discourse-cdn.com/v4/letter/m/4af34b/32.png) [@mfries](https://discuss.elastic.co/u/mfries)\
**Post date:** [November 26, 2019, 9:35am UTC](https://discuss.elastic.co/t/problem-filebeat-7-4-0-excesive-syslog-size/208291/21 "2019-11-26T09:35:41Z")

</div>

Ok. I cannot reproduce that here. Because we´re using systemd with journald.

If you cannot stop logging to /var/log/syslog than it´s worth a try to set it explicit to log to a file. Than you´re definetly sure that it´s configured the right way. And it´s easier to read for others (your collegues). Who do not have the knowledge of the defaultbehavior of filebeat.

---

<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 24, 2019, 9:35am UTC](https://discuss.elastic.co/t/problem-filebeat-7-4-0-excesive-syslog-size/208291/22 "2019-12-24T09:35:46Z")

</div>

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

[Previous page](https://discuss.elastic.co/t/problem-filebeat-7-4-0-excesive-syslog-size/208291.md?page=1)