#25684: Runserver doesn't use `LOGGING` configuration
-----------------------------------+------------------------------------
Reporter: fcurella | Owner: fcurella
Type: New feature | Status: assigned
Component: Error reporting | Version: master
Severity: Normal | Resolution:
Keywords: runserver logging | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-----------------------------------+------------------------------------
Comment (by andreif):
1. I believe it would be better to use `django.server` instead of
`django.request.runserver` for logger name:
{{{
INFO django.server: [07/Nov/2015 20:38:22] "GET / HTTP/1.1" 200 2
}}}
vs
{{{
INFO django.request.runserver: [07/Nov/2015 20:38:22] "GET / HTTP/1.1"
200 2
}}}
2. The date-time should probably not be a part of the message since it's
usually configured in formatter. However, by default python logs without
time info. Maybe `LOGGING` dict in `global_settings.py` can have
`django.server` logging config...
{{{
2015-11-07 20:38:22,627 INFO django.server: [07/Nov/2015 20:38:22] "GET /
HTTP/1.1" 200 2
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25684#comment:17>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.a93c0388a335cadeaf2869cd4699d683%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
