# No Event / Alert fired

**URL:** <https://community.graylog.org/t/no-event-alert-fired/14391>\
**Category:** Graylog Central (peer support)\
**Created:** [March 9, 2020, 9:00am UTC](https://community.graylog.org/t/no-event-alert-fired/14391 "2020-03-09T09:00:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![DerBeton](https://avatars.discourse-cdn.com/v4/letter/d/3ab097/32.png) [@DerBeton](https://community.graylog.org/u/DerBeton)\
**Post date:** [March 9, 2020, 9:00am UTC](https://community.graylog.org/t/no-event-alert-fired/14391/1 "2020-03-09T09:00:38Z")

</div>

Hey Graylog Community

We have a one node Graylog Setup with Docker.

Versions:

- **graylog:3.2.2**
- **mongo:3**
- **elasticsearch-oss:6.8.5**

Our environment has only 2 clients connected until now and our log rate is below 1 log/minute.

We have an alert set up, which should be triggered as soon as a critical error enters graylog (Search every minute for 1 minute).  
The Problem is, that the event is only fired, when there is another event after the critical one.  
For now we solved the problem with a Random HTTP Message Input but that’s not a “nice” solution, because every log is stored in elasticsearch and overall its “messier”.

My Questions are:

- Is there a way to delete Random HTTP Messages instandly without storing them in elasticsearch?
- Is there another solution to solve this Problem? Disabling Journaling on 1 node isn’t the best idea I think?

Thanks 🙂

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/3X/c/7/c7c09c6b5099570133d6502b83f50ba4430de5b6.png) [@system](https://community.graylog.org/u/system)\
**Post date:** [March 23, 2020, 9:00am UTC](https://community.graylog.org/t/no-event-alert-fired/14391/2 "2020-03-23T09:00:38Z")

</div>

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