#33897: django.request log for all requests
-------------------------------+--------------------------------------
Reporter: Tim Ioannidis | Owner: nobody
Type: New feature | Status: closed
Component: HTTP handling | Version: 4.0
Severity: Normal | Resolution: wontfix
Keywords: logging | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => wontfix
* component: Utilities => HTTP handling
Comment:
> What's the rationale behind only logging responses with `django.request`
if status code is >= 400?
As far as I'm aware web server logs are appropriate place for logging all
responses. It's not something that must be included in Django itself (see
also #12012 and LoggingProposal).
> Do you think we could make this a setting that a user can configure?
Creating a new setting is always controversial because we already have
plenty of them. Moreover, you can find many 3rd-party packages (e.g.
`django-request-logging`, `django-request`) that will help you to achieve
this. You can also add a custom middleware that will log all responses in
the `django.request` logger.
--
Ticket URL: <https://code.djangoproject.com/ticket/33897#comment:2>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701826d903256-2c59edbe-3d02-4660-a4ae-e1b1e27fe345-000000%40eu-central-1.amazonses.com.
