# Filebeat addad an entry multiple times

**URL:** <https://discuss.elastic.co/t/filebeat-addad-an-entry-multiple-times/118035>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [February 1, 2018, 2:04pm UTC](https://discuss.elastic.co/t/filebeat-addad-an-entry-multiple-times/118035 "2018-02-01T14:04:52Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mojster](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mojster/32/21209_2.png) [@Mojster](https://discuss.elastic.co/u/Mojster)\
**Post date:** [February 1, 2018, 2:04pm UTC](https://discuss.elastic.co/t/filebeat-addad-an-entry-multiple-times/118035/1 "2018-02-01T14:04:53Z")

</div>

I'm running ES stack 6.1.2.

Filebeat is adding some lines multiple time from our log.  
The lines are added with the same @timestamp.

How can I prevent this. This never appeared on 5.x versions.

---

<div class="post-metadata">

**Author:** ![Mojster](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mojster/32/21209_2.png) [@Mojster](https://discuss.elastic.co/u/Mojster)\
**Post date:** [February 2, 2018, 10:19am UTC](https://discuss.elastic.co/t/filebeat-addad-an-entry-multiple-times/118035/2 "2018-02-02T10:19:33Z")

</div>

It was my mistake so I edited this post.  
This method is working. And I could solve my problem with it.

> **[Little Logstash Lessons: Handling Duplicates](https://www.elastic.co/blog/logstash-lessons-handling-duplicates)**
>
> Approaches for de-duplicating data in Elasticsearch using Logstash. We also go into examples of how you can use IDs in Elasticsearch Output.

---

<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:** [March 2, 2018, 10:19am UTC](https://discuss.elastic.co/t/filebeat-addad-an-entry-multiple-times/118035/3 "2018-03-02T10:19:42Z")

</div>

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