# Duplication in Filebeat to Elasticsearch data pushing

**URL:** <https://discuss.elastic.co/t/duplication-in-filebeat-to-elasticsearch-data-pushing/110605>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [December 7, 2017, 4:19am UTC](https://discuss.elastic.co/t/duplication-in-filebeat-to-elasticsearch-data-pushing/110605 "2017-12-07T04:19:13Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![john.akash](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/john.akash/32/18707_2.png) [@john.akash](https://discuss.elastic.co/u/john.akash)\
**Post date:** [December 7, 2017, 4:19am UTC](https://discuss.elastic.co/t/duplication-in-filebeat-to-elasticsearch-data-pushing/110605/1 "2017-12-07T04:19:13Z")

</div>

Hi Team,

I am using a solution that reads JSON logs by filebeat and push the data to ES without logstasg. While I am checking I can see **duplication in documentation**.

Could you please let us know how can we configure a uniq id (similar to the document id in logstash _ **"document\_id =\> "%{eventid}-%{time}""** _) to avoid duplication in this method?

---

<div class="post-metadata">

**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\
**Post date:** [December 7, 2017, 12:48pm UTC](https://discuss.elastic.co/t/duplication-in-filebeat-to-elasticsearch-data-pushing/110605/2 "2017-12-07T12:48:21Z")

</div>

Setting IDs or Unique IDs are not yet supported. Deduplication via IDs is something we will definitely want to support in the future.

The duplicate events are normally a sign of I/O errors while ingesting data. Have you checked your logs for I/O errors? Maybe it's a matter of queue/bulk size for processing events in Elasticsearch.

---

<div class="post-metadata">

**Author:** ![john.akash](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/john.akash/32/18707_2.png) [@john.akash](https://discuss.elastic.co/u/john.akash)\
**Post date:** [December 7, 2017, 7:25pm UTC](https://discuss.elastic.co/t/duplication-in-filebeat-to-elasticsearch-data-pushing/110605/3 "2017-12-07T19:25:53Z")

</div>

Could you please provide us on ETA on that?

---

<div class="post-metadata">

**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\
**Post date:** [December 8, 2017, 11:59am UTC](https://discuss.elastic.co/t/duplication-in-filebeat-to-elasticsearch-data-pushing/110605/4 "2017-12-08T11:59:12Z")

</div>

No ETA. Some related work is done in the PRs [#5811](https://github.com/elastic/beats/pull/5811) and [#5844](https://github.com/elastic/beats/pull/5844), but there is still some more work required for supporting setting document IDs in beats.

---

<div class="post-metadata">

**Author:** ![john.akash](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/john.akash/32/18707_2.png) [@john.akash](https://discuss.elastic.co/u/john.akash)\
**Post date:** [December 8, 2017, 7:05pm UTC](https://discuss.elastic.co/t/duplication-in-filebeat-to-elasticsearch-data-pushing/110605/5 "2017-12-08T19:05:09Z")

</div>

@steffens Ok, cool. Waiting for that release.

---

<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:** [December 28, 2017, 4:19am UTC](https://discuss.elastic.co/t/duplication-in-filebeat-to-elasticsearch-data-pushing/110605/6 "2017-12-28T04:19:15Z")

</div>

This topic was automatically closed after 21 days. New replies are no longer allowed.