#21949: Django doesn't log much at high verbosity levels
-------------------------------+--------------------------------------
Reporter: gcc | Owner: nobody
Type: New feature | Status: new
Component: Uncategorized | Version: 1.6
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by russellm):
Regarding your specific points here:
1) In the case of an error, the error handler *does* contain a full
record of the request, including the URL, all GET and POST arguments, a
summary of the FILES, the WSGI environment, all settings (redacted for
passwords, etc), and the stack trace that resulted. By default this is
sent via email, but it's handled via a logger, so you can point it at a
file, or an external web service (like Sentry) if you want to. Is there a
compelling case for dumping this data for *successful* requests?
2) "We need more DEBUG messages so we can tell that logging is configured
correctly" doesn't strike me as a very strong argument.
3) You should probably be looking at gunicorn or uWSGI as the piece
responsible for extra logging, but point taken. mod_dumpio is the magic
keyword for apache. However, as pointed out in (1), full request
information *is* provided in the case of
4) I'd hope that too, but nothing is free; data trumps everything. It
would be helpful to have some good real-world metrics to guide this, and
other discussions. We've got indicative impact numbers for signals (which
is the other extension point that is asked for regularly); it would be
good to have similar numbers for logging.
--
Ticket URL: <https://code.djangoproject.com/ticket/21949#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/061.f42aee2e21ed55fb437bd23c085afdca%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
