# Disable sincedb/Ingesting data from files with same name

**URL:** <https://discuss.elastic.co/t/disable-sincedb-ingesting-data-from-files-with-same-name/163632>\
**Category:** Logstash\
**Created:** [January 9, 2019, 11:30pm UTC](https://discuss.elastic.co/t/disable-sincedb-ingesting-data-from-files-with-same-name/163632 "2019-01-09T23:30:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![wwalker](https://avatars.discourse-cdn.com/v4/letter/w/43a26b/32.png) [@wwalker](https://discuss.elastic.co/u/wwalker)\
**Post date:** [January 9, 2019, 11:30pm UTC](https://discuss.elastic.co/t/disable-sincedb-ingesting-data-from-files-with-same-name/163632/1 "2019-01-09T23:30:06Z")

</div>

I have a need to ingest logs from multiple computers where the filename is always the same. I seem to be running into an issue (with file input) where after the first file is ingested, followup files are ignored because they have the same name. How can I effectively disable (or genuinely disable) the sincedb function of the file input or is there a better method to accomplish this? This is running on a Windows OS and setting sincedb to /null ended up creating a file called null at the root of the drive. I intend to deploy a script that manually forces a process to occur on a remote machine, collect the log file, and then put it in the file ingest folder.

---

<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:** [February 6, 2019, 11:30pm UTC](https://discuss.elastic.co/t/disable-sincedb-ingesting-data-from-files-with-same-name/163632/2 "2019-02-06T23:30:06Z")

</div>

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