good 404 vs bad 404

In systems which are accessed only via intranet we used to monitor http 404 responses.

Every time a 404 happens, an issue in our monitoring gets created.

This worked well in the past.

Now we have cases where a 404 is valid or should be ignored. No issue in the monitoring should be visible.

You could apply "separation of concerns" and keep on reporting all 404 responses
and do the filtering in the monitoring area.

But on the other hand the code knows more. I have places where I know that
this 404 should be ignored.

I am biased where the problem should get solved:
 
 - inside django app
 - inside monitoring


What do you think?

Does anybody make a differenence between "good 404 vs bad 404"?

Regards,
  Thomas

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/fb152b91-ee44-42aa-8304-fb43eba43be1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.