# Identify Files Already Parsed by Logstash
**URL:** https://discuss.elastic.co/t/identify-files-already-parsed-by-logstash/45766
**Category:** Logstash
**Created:** [March 30, 2016, 8:42am UTC](https://discuss.elastic.co/t/identify-files-already-parsed-by-logstash/45766 "2016-03-30T08:42:05Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@gringo](https://discuss.elastic.co/u/gringo)
#### Post date: [March 30, 2016, 8:42am UTC](https://discuss.elastic.co/t/identify-files-already-parsed-by-logstash/45766/1 "2016-03-30T08:42:05Z")
How do I know if a file is already parsed by logstash? I want to create a setup such that once a file is copied into a folder I will parsed it and move it to another location for archiving
---
### Author:  [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [March 30, 2016, 8:58am UTC](https://discuss.elastic.co/t/identify-files-already-parsed-by-logstash/45766/2 "2016-03-30T08:58:58Z")
There's no really good way of doing this, but you could inspect the sincedb files to get a sense of Logstash's progress. You can correlate the inode numbers in those files with the inodes of the files that you want to move out of the way. See the file input documentation for more on sincedb.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 5:04am UTC](https://discuss.elastic.co/t/identify-files-already-parsed-by-logstash/45766/3 "2017-07-06T05:04:47Z")