# Kibana filters running as ES Queries **URL:** \ **Category:** Kibana\ **Created:** [September 28, 2016, 10:46am UTC](https://discuss.elastic.co/t/kibana-filters-running-as-es-queries/61685 "2016-09-28T10:46:35Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Or\_Weinberger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/or_weinberger/32/11850_2.png) [@Or\_Weinberger](https://discuss.elastic.co/u/Or_Weinberger)\ **Post date:** [September 28, 2016, 10:46am UTC](https://discuss.elastic.co/t/kibana-filters-running-as-es-queries/61685/1 "2016-09-28T10:46:35Z")
Running Kibana 5-alpha5, in the Discover tab when you add a filter to your search (for example, by clicking the + sign next to a field), it filters out the results according to that value, but looking at the request that is actually being sent to the server shows that Kibana doesn't add an Elasticsearch filter, but it adds a match query instead. Why is that? Since filtering on an field means exact matching it, wouldn't it be beneficial to run it as a filter? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:37pm UTC](https://discuss.elastic.co/t/kibana-filters-running-as-es-queries/61685/2 "2017-07-06T13:37:58Z")