I'd argue that all of the 404s are bad - if your tools are generating broken links isn't it better to fix that than to band-aid it with what is a "good" vs "bad" 404?
On Thu, Mar 2, 2017 at 11:10 AM, Antonis Christofides < [email protected]> wrote: > If what you want is locate broken links and ignore 404s resulting from > emails, then Django's broken link detection functionality > <https://docs.djangoproject.com/en/1.10/howto/error-reporting/#errors> is > probably all that you need, unless you really need to do it in monitoring > and you can't possibly do it with emails. Ignoring 404s with no referrer > has been added to 1.9. If I wanted to do this and I was using 1.8 I'd > probably try to monkey-patch Django with backported code from 1.9. > > Regards, > > Antonis > > Antonis Christofideshttp://djangodeployment.com > > On 03/01/2017 06:21 PM, guettli wrote: > > > > 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 [email protected]. > To post to this group, send email to [email protected]. > 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 > <https://groups.google.com/d/msgid/django-users/74679d0f-aa42-4885-8702-c8f6caf6a6bc%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Django users" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/django-users/Ew7hDj-ELaw/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > 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/172dd6e3-a6a9-145c-4963-063100332cd1% > 40djangodeployment.com > <https://groups.google.com/d/msgid/django-users/172dd6e3-a6a9-145c-4963-063100332cd1%40djangodeployment.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. To post to this group, send email to [email protected]. 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/CAFRq704FmGtr40Km-aX%2Bj09RzWQLmXneDYohm%3D_DbOfCR6whyg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
