# Duplicate content in indexes

**URL:** <https://discuss.elastic.co/t/duplicate-content-in-indexes/131821>\
**Category:** Logstash\
**Created:** [May 14, 2018, 11:23pm UTC](https://discuss.elastic.co/t/duplicate-content-in-indexes/131821 "2018-05-14T23:23:23Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![motts](https://avatars.discourse-cdn.com/v4/letter/m/839c29/32.png) [@motts](https://discuss.elastic.co/u/motts)\
**Post date:** [May 15, 2018, 9:00pm UTC](https://discuss.elastic.co/t/duplicate-content-in-indexes/131821/5 "2018-05-15T21:00:15Z")

</div>

I had this issue myself. Turns out, there was an error in the Kibana index in Elasticseaerch. I got rid of that Kibana index and data was going to the correct indices.

Make sure the only files in /logstash/logstash.conf directory are only .conf files for logstash as well.

See here:

> [@Data is sent to created index and the default index](https://discuss.elastic.co/t/data-is-sent-to-created-index-and-the-default-index/113845):
>
> I have an interesting issue where data is being sent to the new index and also the old default index. I am using Elasticsearch 2.4 and here is my output file: output { if [type] == "Corporate" { elasticsearch { hosts =\> ["localhost:9200"] index =\> "corp\_windows\_events-%{+YYYY-MM-dd}" } } else { elasticsearch { hosts =\> ["localhost:9200"] } } } I checked both indic…

---

_[View the full topic](https://discuss.elastic.co/t/duplicate-content-in-indexes/131821)._