# Duplicate content when using azure-blob-storage input

**URL:** <https://discuss.elastic.co/t/duplicate-content-when-using-azure-blob-storage-input/344046>\
**Category:** Beats\
**Tags:** beats-module, filebeat\
**Created:** [September 28, 2023, 8:25am UTC](https://discuss.elastic.co/t/duplicate-content-when-using-azure-blob-storage-input/344046 "2023-09-28T08:25:27Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![djesus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/djesus/32/113663_2.png) [@djesus](https://discuss.elastic.co/u/djesus)\
**Post date:** [October 11, 2023, 7:00am UTC](https://discuss.elastic.co/t/duplicate-content-when-using-azure-blob-storage-input/344046/5 "2023-10-11T07:00:34Z")

</div>

Hi @suman.kumar

thanks for your reply! filebeat is sending data to Graylog which in turn stores it in Elasticsearch. I guess i could give it a try to setup a logstash instance as a middle step however this would add complexity to the solution and add another possible point of failure.

also im seeing a worse issue, when this is happening ([403 auth error when using the filebeat input azure-blob-storage (error: Request date header too old)](https://discuss.elastic.co/t/403-auth-error-when-using-the-filebeat-input-azure-blob-storage-error-request-date-header-too-old/343089)) and i have to restart filebeat, it will re download everything again from the blob storage.... it seems that the local filebeat db keeping state of what was already downloaded gets corrupted.

---

_[View the full topic](https://discuss.elastic.co/t/duplicate-content-when-using-azure-blob-storage-input/344046)._