# Urgent: reparsing log files with Logstash?

**URL:** <https://discuss.elastic.co/t/urgent-reparsing-log-files-with-logstash/135109>\
**Category:** Logstash\
**Created:** [June 8, 2018, 8:12am UTC](https://discuss.elastic.co/t/urgent-reparsing-log-files-with-logstash/135109 "2018-06-08T08:12:56Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michel99\_7](https://avatars.discourse-cdn.com/v4/letter/m/97f17d/32.png) [@Michel99\_7](https://discuss.elastic.co/u/Michel99_7)\
**Post date:** [June 8, 2018, 8:12am UTC](https://discuss.elastic.co/t/urgent-reparsing-log-files-with-logstash/135109/1 "2018-06-08T08:12:56Z")

</div>

Dear all,

Here is the context

- OS: Linux
- Kibana: v6.1.1
- Elasticsearch & Logstash: v6.1.1
- Browser: Google Chrome Version 64.0.3282.186

- Context: we are indexing data by using Logstash and the file input plugin for .log files (persistency managed via sincedb files); due to problems on the process that provide log files, we sometimes need to reindex log files in ES from a certain period, instead of reindexing all of them (several Gb)

- Question: is there a way to configure LS so that log files are reparsed from a certain period? we assume that our sincedb file can be updated by removing all lines from a certain INODE reference; but we faced a major problem: the reference of the INODE within the sincedb file has nothing to do with the INODE reference we get by using the ls -i command. Any hint?

Many thanks in advance.

---

<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:** [July 6, 2018, 8:12am UTC](https://discuss.elastic.co/t/urgent-reparsing-log-files-with-logstash/135109/2 "2018-07-06T08:12:59Z")

</div>

Closed on July 6, 2018, 8:12am UTC

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