# The old Windows Event Log has been detected again

**URL:** <https://discuss.elastic.co/t/the-old-windows-event-log-has-been-detected-again/155821>\
**Category:** Logstash\
**Created:** [November 8, 2018, 5:43am UTC](https://discuss.elastic.co/t/the-old-windows-event-log-has-been-detected-again/155821 "2018-11-08T05:43:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![foxtrot](https://avatars.discourse-cdn.com/v4/letter/f/5fc32e/32.png) [@foxtrot](https://discuss.elastic.co/u/foxtrot)\
**Post date:** [November 8, 2018, 5:43am UTC](https://discuss.elastic.co/t/the-old-windows-event-log-has-been-detected-again/155821/1 "2018-11-08T05:43:30Z")

</div>

I am using the Logstash 2.4.1 version.  
When Winodws Event Log matches the setting condition on the window server OS, a trap is sent.

The problem is that once detected Windows Event logs are detected again and forward traps again.  
That log is not displayed in the latest Windows Event Log.

This is irregular and not frequent.

Have you experienced this kind of thing?

Please let me know if you know the solution and cause.

---

<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:** [December 6, 2018, 5:43am UTC](https://discuss.elastic.co/t/the-old-windows-event-log-has-been-detected-again/155821/2 "2018-12-06T05:43:39Z")

</div>

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