#34236: Django logging when in production with Gunnicron
-------------------------------+--------------------------------------
Reporter: Derek | Owner: nobody
Type: Uncategorized | Status: closed
Component: Documentation | Version: 4.1
Severity: Normal | Resolution: invalid
Keywords: logging | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => invalid
Comment:
Replying to [ticket:34236 Derek]:
> I was trying to configure access logs using Django logging as per
documentation https://docs.djangoproject.com/en/4.1/howto/logging/
> I wanted to collect all access logs from INFO. It works perfectly when
in development mode. However, when I switched to Gunnicron in production,
I got only warnings and higher status logs.
It's not strictly related with `Gunicorn`, and it's already
[https://docs.djangoproject.com/en/stable/ref/logging/#django-server
documented] that the `django.server` logger logs ''"messages related to
the handling of requests received by the server invoked by the
**runserver** command."''
--
Ticket URL: <https://code.djangoproject.com/ticket/34236#comment:4>
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/0107018570f4332d-ed2befbd-67f8-4d57-b22e-146838cb52d7-000000%40eu-central-1.amazonses.com.
