# Filtering Winlogbeat on Event ID

**URL:** <https://discuss.elastic.co/t/filtering-winlogbeat-on-event-id/43899>\
**Category:** Beats\
**Tags:** winlogbeat\
**Created:** [March 9, 2016, 1:57pm UTC](https://discuss.elastic.co/t/filtering-winlogbeat-on-event-id/43899 "2016-03-09T13:57:53Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\
**Post date:** [March 9, 2016, 2:27pm UTC](https://discuss.elastic.co/t/filtering-winlogbeat-on-event-id/43899/2 "2016-03-09T14:27:56Z")

</div>

That's a lot of machines. See the discussion here: [Filtering Winlogbeat Events](https://discuss.elastic.co/t/filtering-winlogbeat-events/41116)

Summarizing that thread, a filtering feature is being added to all beats. Relevant here is `drop_event` in the [proposal](https://github.com/elastic/beats/issues/45). Additionally there is a [request](https://github.com/elastic/beats/issues/1054) for using XPath queries in Winlogbeat, but that's further out ([#1053](https://github.com/elastic/beats/issues/1053) is first in line).

At the current time you need to use Logstash to do filtering.

---

_[View the full topic](https://discuss.elastic.co/t/filtering-winlogbeat-on-event-id/43899)._