# Filebeat Logging: Include filenames in the log

**URL:** <https://discuss.elastic.co/t/filebeat-logging-include-filenames-in-the-log/185285>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [June 11, 2019, 9:53pm UTC](https://discuss.elastic.co/t/filebeat-logging-include-filenames-in-the-log/185285 "2019-06-11T21:53:11Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![seth.yes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/seth.yes/32/11788_2.png) [@seth.yes](https://discuss.elastic.co/u/seth.yes)\
**Post date:** [June 11, 2019, 9:53pm UTC](https://discuss.elastic.co/t/filebeat-logging-include-filenames-in-the-log/185285/1 "2019-06-11T21:53:12Z")

</div>

Is there a way to configure the logging to include the filename when reporting an error?

I'm using an instance of Filebeat (v6.2) which tails somewhere around 80 different file paths. Currently when errors are reported, the name of which file Filebeat is reporting an error on isn't included. Parsing 80 different files to determine the issue is cumbersome and inefficient.

---

<div class="post-metadata">

**Author:** ![shaunak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shaunak/32/6643_2.png) [@shaunak](https://discuss.elastic.co/u/shaunak)\
**Post date:** [June 13, 2019, 10:52pm UTC](https://discuss.elastic.co/t/filebeat-logging-include-filenames-in-the-log/185285/2 "2019-06-13T22:52:08Z")

</div>

Could you provide a sample of the parsing errors as they are currently being reported (without the filename) in your Filebeat log?

Thanks,

Shaunak

---

<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 11, 2019, 10:52pm UTC](https://discuss.elastic.co/t/filebeat-logging-include-filenames-in-the-log/185285/3 "2019-07-11T22:52:12Z")

</div>

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