# Logstash reading events from March 14th on March 16th

**URL:** <https://discuss.elastic.co/t/logstash-reading-events-from-march-14th-on-march-16th/375982>\
**Category:** Logstash\
**Created:** [March 16, 2025, 5:41pm UTC](https://discuss.elastic.co/t/logstash-reading-events-from-march-14th-on-march-16th/375982 "2025-03-16T17:41:24Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [March 16, 2025, 6:30pm UTC](https://discuss.elastic.co/t/logstash-reading-events-from-march-14th-on-march-16th/375982/6 "2025-03-16T18:30:54Z")

</div>

> [@devops\_training](#):
>
> "reason"=\>"index [http\_server-2025.03.14] blocked by: [TOO\_MANY\_REQUESTS/12/disk usage exceeded flood-stage watermark, index has read-only-allow-delete block];"}}`

You can read about what you would do if elasticsearch returned that error [here](https://discuss.elastic.co/t/error-disk-usage-exceeded-flood-stage-watermark-index-has-read-only-allow-delete-block/323357/2). If you want advice specific to opensearch then post in their support forum.

---

_[View the full topic](https://discuss.elastic.co/t/logstash-reading-events-from-march-14th-on-march-16th/375982)._