# Are new input files automatically enabled with the reload feature?

**URL:** <https://discuss.elastic.co/t/are-new-input-files-automatically-enabled-with-the-reload-feature/141122>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [July 23, 2018, 9:20am UTC](https://discuss.elastic.co/t/are-new-input-files-automatically-enabled-with-the-reload-feature/141122 "2018-07-23T09:20:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![andreastoom](https://avatars.discourse-cdn.com/v4/letter/a/7c8e57/32.png) [@andreastoom](https://discuss.elastic.co/u/andreastoom)\
**Post date:** [July 23, 2018, 9:20am UTC](https://discuss.elastic.co/t/are-new-input-files-automatically-enabled-with-the-reload-feature/141122/1 "2018-07-23T09:20:59Z")

</div>

Hi,

I am trying to get some confirmation whether filebeat automatically adds new input files that are dropped in a config path with a GLOB pattern or not ? In our case we will have a number of applications that will be running on a shared host and during deployment we would like to drop input files for each application in a special folder that will be picked up by the filebeat process without it having to be restarted.

According to another thread ([Clarifications regarding reload configuration](https://discuss.elastic.co/t/clarifications-regarding-reload-configuration/106284)) the reloading feature in filebeat should cover file content changes in files that existed during init of filebeat aswell as newly added input files while the filebeat process is running. Unfortunately I cannot get this to work.

I have checked the following:

- Running the latest version of filebeat, 6.3.1 on Linux
- The file permissions of the input file is 0440 with ownership belonging to the filebeat user
- The input file works when the filebeat process is restarted

Snippets of my config looks like this:

filebeat.yml

```
filebeat:
  config:
    inputs:
      enabled: true
      path: /opt/filebeat-test/config/inputs/*.yml
      reload:
       enable: true
       period: 10s

```

file permissions

```
drwxr-x---. 2 filebeat-local-user filebeat-local-group 48 Jul 23 10:12 .
drwxr-x---. 4 filebeat-local-user filebeat-local-group 52 Jul 23 10:12 ..
-r--r-----. 1 filebeat-local-user filebeat-local-group 101 Jul 23 10:17 filebeat-log.yml
-r--r-----. 1 filebeat-local-user filebeat-local-group 63 Jul 23 09:56 syslog.yml

```

Any ideas what could be wrong ?

/Andreas

---

<div class="post-metadata">

**Author:** ![andreastoom](https://avatars.discourse-cdn.com/v4/letter/a/7c8e57/32.png) [@andreastoom](https://discuss.elastic.co/u/andreastoom)\
**Post date:** [July 23, 2018, 10:56am UTC](https://discuss.elastic.co/t/are-new-input-files-automatically-enabled-with-the-reload-feature/141122/2 "2018-07-23T10:56:45Z")

</div>

Hi,

I managed to spot my own error - i missed the last 'd' in the 'reload.enabled' property for the reload configuration. Now when the configuration is correct I can confirm that everything is working as expected!

/Andreas

---

<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:** [August 20, 2018, 10:56am UTC](https://discuss.elastic.co/t/are-new-input-files-automatically-enabled-with-the-reload-feature/141122/3 "2018-08-20T10:56:53Z")

</div>

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