# Capturing missed logs after Elasticsearch read-only reset

**URL:** <https://discuss.elastic.co/t/capturing-missed-logs-after-elasticsearch-read-only-reset/201096>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [September 25, 2019, 7:44pm UTC](https://discuss.elastic.co/t/capturing-missed-logs-after-elasticsearch-read-only-reset/201096 "2019-09-25T19:44:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![MinnMoto](https://avatars.discourse-cdn.com/v4/letter/m/e9c0ed/32.png) [@MinnMoto](https://discuss.elastic.co/u/MinnMoto)\
**Post date:** [September 25, 2019, 7:44pm UTC](https://discuss.elastic.co/t/capturing-missed-logs-after-elasticsearch-read-only-reset/201096/1 "2019-09-25T19:44:18Z")

</div>

I ran into the situation 2 days ago where Elasticsearch kicked in to a " **FORBIDDEN/12/index read-only**" episode. I freed up space, reset the _read\_only\_allow\_delete_ and got logs capturing again. However, I had about 12 hours on my servers where logging was missed.

Can I give Filebeat parameters to capture the logs to Elasticsearch for a period of time? To get logs pushed in during the "read-only" period?

Thanks in advance!

---

<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 23, 2019, 7:44pm UTC](https://discuss.elastic.co/t/capturing-missed-logs-after-elasticsearch-read-only-reset/201096/2 "2019-10-23T19:44:27Z")

</div>

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