I am wondering if it would be a good idea to save a copy of *404s* in
database instead of sending the email out to the ADMIN.

The reason is, while I see a notification of some sort beneficial, with
sites that items are added and deleted on a regular basis, all those 404
messages (emails) can be costly and annoying at times. Not knowing about
your missing links is not ideal either.

An App that keeps a copy of all the 404s and admin can indicate to receive
a single notification per (day/week or # new 404s) would be great.

*Sentry* is great for 5xx logs, but I am looking to have a built-in feature
in Django for 404s.

I often get a russian bot that tries lot of specific links, while another
bot (spammer) tries different links so they can exploit the site.

With current setup (email to ADMIN), I get 10-20 emails for a single bot
scanning the site.
I can't afford not notifying myself of the 404s either, but I don't want to
see all those bogus 404s to generate emails. IGNORABLE_404_URLS is used now
and it has its limits.

Of course I can role out my own app for this, but I think it would
be beneficial to the community if Django did this out of the box.

Now, the $64 K question: is Django a good place for this?

Appreciate your feedback.

Val

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" 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 http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to