# Filebeat and missing logs

**URL:** <https://discuss.elastic.co/t/filebeat-and-missing-logs/105809>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [October 30, 2017, 8:59pm UTC](https://discuss.elastic.co/t/filebeat-and-missing-logs/105809 "2017-10-30T20:59:55Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![StivOstenberg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stivostenberg/32/4681_2.png) [@StivOstenberg](https://discuss.elastic.co/u/StivOstenberg)\
**Post date:** [October 30, 2017, 8:59pm UTC](https://discuss.elastic.co/t/filebeat-and-missing-logs/105809/1 "2017-10-30T20:59:55Z")

</div>

We are trying to deploy Filebeat to a steaming pile of Beanstalk instances. In our case, different instances have different applications, and perhaps different logs to monitor. The process for automating a per-app custom filebeat config file is painful with beanstalk. We were considering whether if might make sense to just list all the possible config files in a single filebeat config. Would filebeat just shrug off the missing files, or would it complain continuously?

---

<div class="post-metadata">

**Author:** ![kvch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kvch/32/72058_2.png) [@kvch](https://discuss.elastic.co/u/kvch)\
**Post date:** [October 31, 2017, 3:48pm UTC](https://discuss.elastic.co/t/filebeat-and-missing-logs/105809/2 "2017-10-31T15:48:09Z")

</div>

Filebeat does not complain if it cannot find a file. However, in case the file is present on the filesystem but it cannot be accessed, FB logs error messages every time it tries to read from it.

---

<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:** [November 28, 2017, 3:48pm UTC](https://discuss.elastic.co/t/filebeat-and-missing-logs/105809/3 "2017-11-28T15:48:50Z")

</div>

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