# Apache 404 response code in filebeat **URL:** \ **Category:** Elasticsearch\ **Created:** [August 3, 2016, 6:50pm UTC](https://discuss.elastic.co/t/apache-404-response-code-in-filebeat/57143 "2016-08-03T18:50:11Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![kartikvelastic](https://avatars.discourse-cdn.com/v4/letter/k/7ba0ec/32.png) [@kartikvelastic](https://discuss.elastic.co/u/kartikvelastic)\ **Post date:** [August 3, 2016, 6:50pm UTC](https://discuss.elastic.co/t/apache-404-response-code-in-filebeat/57143/1 "2016-08-03T18:50:11Z")
I am using filebeat with ES as output. I have specified: input\_type: log document\_type: apache paths: - /var/log/httpd/\*\_log in /etc/filebeat/filebeat.yml and am able to successfully see results in Kibana. I am however playing around with "Watcher" and trying to create a watch based on an http return code of 404, I see no field in my Kibana filebeat results that corresponds to and only to "404", something like "response", I am afraid I am missing something because filebeat and ELK are BIG products, and help would be appreciated. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [August 5, 2016, 12:25am UTC](https://discuss.elastic.co/t/apache-404-response-code-in-filebeat/57143/2 "2016-08-05T00:25:02Z")
Given you are processing the logs directly to ES it won't be separating the events and creating separate fields. You will need so push them through Logstash instead. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 10:29pm UTC](https://discuss.elastic.co/t/apache-404-response-code-in-filebeat/57143/3 "2017-07-05T22:29:56Z")
Closed on July 5, 2017, 10:29pm UTC