# Input File Path (not working) vs Input Beats (working) all conf setting are the same but Input

**URL:** https://discuss.elastic.co/t/input-file-path-not-working-vs-input-beats-working-all-conf-setting-are-the-same-but-input/164800
**Category:** Logstash
**Created:** [January 18, 2019, 1:21pm UTC](https://discuss.elastic.co/t/input-file-path-not-working-vs-input-beats-working-all-conf-setting-are-the-same-but-input/164800 "2019-01-18T13:21:18Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)
#### Post date: [January 18, 2019, 2:54pm UTC](https://discuss.elastic.co/t/input-file-path-not-working-vs-input-beats-working-all-conf-setting-are-the-same-but-input/164800/4 "2019-01-18T14:54:46Z")

</div>

Enable trace level logging and look for filewatch. You can turn on trace globally on the command line or through logstash.yml, or you can enable trace just for the filewatch modules through the api as described [here](https://discuss.elastic.co/t/logstash-wildcards-regex-not-working/164204/19?u=badger).

---

_[View the full topic](https://discuss.elastic.co/t/input-file-path-not-working-vs-input-beats-working-all-conf-setting-are-the-same-but-input/164800)._