Am Mittwoch, 1. März 2017 10:54:38 UTC+1 schrieb Antonis Christofides: > > My gut feeling says you should treat this in monitoring, however here are > some questions: > > 1) Why do you monitor 404s at all? > > 2) Could you give some examples of 404s that are valid or should be > ignored? > > I monitor 404 since it this question is about an application which runs only in the intranet.
No robots or other strange request come in. 99% of all requests are inside the application. If there is a 404, then it is very likely that our application creates broken links. Since we use reverse() every this is very seldom. Up to now monitoring 404 was nice to have. But now there are some parts where too many 404 responses get returned. Concrete example: we render HTML mails. They often contain broken links. I don't want to report these. Can you understand my use case now? If not, please ask. -- 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+unsubscr...@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/74679d0f-aa42-4885-8702-c8f6caf6a6bc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
