# Changes to config file not updating the data in kibana

**URL:** <https://discuss.elastic.co/t/changes-to-config-file-not-updating-the-data-in-kibana/229572>\
**Category:** Logstash\
**Created:** [April 24, 2020, 4:30am UTC](https://discuss.elastic.co/t/changes-to-config-file-not-updating-the-data-in-kibana/229572 "2020-04-24T04:30:56Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nani\_20](https://avatars.discourse-cdn.com/v4/letter/n/4491bb/32.png) [@Nani\_20](https://discuss.elastic.co/u/Nani_20)\
**Post date:** [April 24, 2020, 4:30am UTC](https://discuss.elastic.co/t/changes-to-config-file-not-updating-the-data-in-kibana/229572/1 "2020-04-24T04:30:56Z")

</div>

Hello All,

I am using the latest version of logstash(7.6.2). I tried uploading a sample data and was able to successfully upload it into the elasticsearch using logstash(enabled auto-reload) and was able to see the index in the Kibana interface.

But, when I make changes to the below config file, I was unable to see the updated data in the Kibana interface. I was trying to remove the **mutate filter plugin** and the logstash pipeline reloaded but the data in Kibana is not updated. Interestingly it didn't throw up any errors.

**Sample.conf**

```auto
    input{
    file{
    	path => "/usr/local/Cellar/sample.log"
    	start_position => "beginning"
    }
    }

    filter{
    	grok{
    		match => ["message", "%{TIMESTAMP_ISO8601:timestamp_string}%{SPACE}%{GREEDYDATA:line}"]
    	}
    	date{
    		match => ["timestamp_string", "ISO8601"]
    	}
    	mutate{
    		remove_field => [message, timestamp_string]
    	}
    }
    output{
    elasticsearch{
    	hosts => ["localhost:9200"]
    	index => "sample"
    }
    stdout{
    	codec => rubydebug
    }
    }

```

Any help here is appreciated. TIA

**P.S. - I am new to ElasticSearch 😃**

---

<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:** [April 24, 2020, 4:55pm UTC](https://discuss.elastic.co/t/changes-to-config-file-not-updating-the-data-in-kibana/229572/2 "2020-04-24T16:55:41Z")

</div>

By default a file input runs in tail mode, so it only reads data that is appended to your input file. start\_position only has an effect the first time it sees a file. You may find

```
sincedb_path => "/dev/null"

```

useful, to prevent the input from persisting the in-memory sincedb across reloads.

---

<div class="post-metadata">

**Author:** ![Nani\_20](https://avatars.discourse-cdn.com/v4/letter/n/4491bb/32.png) [@Nani\_20](https://discuss.elastic.co/u/Nani_20)\
**Post date:** [April 24, 2020, 5:28pm UTC](https://discuss.elastic.co/t/changes-to-config-file-not-updating-the-data-in-kibana/229572/3 "2020-04-24T17:28:53Z")

</div>

Thanks a ton! This works but the index in the elasticsearch now has duplicated records i.e. rows from both old and new logstash uploads. I know deleting the index or renaming before every upload would work, but is there any way the index can be updated completely without deletion/renaming?

---

<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:** [April 24, 2020, 5:34pm UTC](https://discuss.elastic.co/t/changes-to-config-file-not-updating-the-data-in-kibana/229572/4 "2020-04-24T17:34:28Z")

</div>

Use a fingerprint filter to combine appropriate fields from the event and then use the result to set the document\_id option on the elasticsearch output. This will result in the documents being overwritten.

---

<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:** [May 22, 2020, 5:34pm UTC](https://discuss.elastic.co/t/changes-to-config-file-not-updating-the-data-in-kibana/229572/5 "2020-05-22T17:34:31Z")

</div>

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