# Packebeat: Unwanted 404 errors for styles, js like resources

**URL:** <https://discuss.elastic.co/t/packebeat-unwanted-404-errors-for-styles-js-like-resources/46243>\
**Category:** Beats\
**Tags:** packetbeat\
**Created:** [April 4, 2016, 1:46pm UTC](https://discuss.elastic.co/t/packebeat-unwanted-404-errors-for-styles-js-like-resources/46243 "2016-04-04T13:46:27Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![krushnat\_khawale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/krushnat_khawale/32/6652_2.png) [@krushnat\_khawale](https://discuss.elastic.co/u/krushnat_khawale)\
**Post date:** [April 4, 2016, 1:46pm UTC](https://discuss.elastic.co/t/packebeat-unwanted-404-errors-for-styles-js-like-resources/46243/1 "2016-04-04T13:46:27Z")

</div>

We are using Topbeat, and are able to successfully dashboard the info.  
But the **'HTTP codes for top queries'** visualization is showing  
a **lot of 404** errors for http request for resources like **styles.css,**  
**jquery-ui.css** etc which we don't want to listen to.  
\*\*Is there any way that we can skip for monitoring specific resources? like \*\*  
**do not watch over css or js requests.**

---

<div class="post-metadata">

**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\
**Post date:** [April 4, 2016, 4:00pm UTC](https://discuss.elastic.co/t/packebeat-unwanted-404-errors-for-styles-js-like-resources/46243/2 "2016-04-04T16:00:40Z")

</div>

you're meaning packetbeat HTTP reports? Why remove errors instead of fixing your HTML? Purpose of monitoring tool like packetbeat is to find and fix these kind of errors. Every request + every 404 requires resources for doing nothing.

---

<div class="post-metadata">

**Author:** ![krushnat\_khawale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/krushnat_khawale/32/6652_2.png) [@krushnat\_khawale](https://discuss.elastic.co/u/krushnat_khawale)\
**Post date:** [April 5, 2016, 5:06am UTC](https://discuss.elastic.co/t/packebeat-unwanted-404-errors-for-styles-js-like-resources/46243/3 "2016-04-05T05:06:43Z")

</div>

Hi, @steffens

Agree with you, but we have priorities, as these 404 are for resources like  
stylesheets, scripts, images; we have we want to focus on showstopper errors.  
We'll fix these 404's later but we got to fix other on priority.

Thanks for your time.

---

<div class="post-metadata">

**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\
**Post date:** [April 5, 2016, 9:25am UTC](https://discuss.elastic.co/t/packebeat-unwanted-404-errors-for-styles-js-like-resources/46243/4 "2016-04-05T09:25:38Z")

</div>

With upcoming v5 alpha1 stack you can use generic filtering support in packetbeat to remove events. Or ingest node support in elasticsearch.

If your're still running on beats 1.x and want to modify/filter events your best option is packetbeat-\>logstash-\>elasticsearch.

---

<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:** [July 5, 2017, 9:53pm UTC](https://discuss.elastic.co/t/packebeat-unwanted-404-errors-for-styles-js-like-resources/46243/5 "2017-07-05T21:53:48Z")

</div>