# Duplicate Events in filebeat/auditbeat

**URL:** <https://discuss.elastic.co/t/duplicate-events-in-filebeat-auditbeat/103290>\
**Category:** Beats\
**Created:** [October 10, 2017, 4:39am UTC](https://discuss.elastic.co/t/duplicate-events-in-filebeat-auditbeat/103290 "2017-10-10T04:39:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![RohanKumbhar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rohankumbhar/32/23649_2.png) [@RohanKumbhar](https://discuss.elastic.co/u/RohanKumbhar)\
**Post date:** [October 10, 2017, 4:39am UTC](https://discuss.elastic.co/t/duplicate-events-in-filebeat-auditbeat/103290/1 "2017-10-10T04:39:50Z")

</div>

Hi Team,

There are few occasion where filebeat/auditbeat is indexing same log event or audit event twice in elasticsearch with different \_id value.

Is this the expected behavior and is there any way to reduce duplication for the same?

Thanks,  
Rohan

---

<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:** [October 31, 2017, 4:40am UTC](https://discuss.elastic.co/t/duplicate-events-in-filebeat-auditbeat/103290/2 "2017-10-31T04:40:07Z")

</div>

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