Opened 23 months ago
Last modified 23 months ago
#34236 closed Uncategorized
Django logging when in production with Gunnicron — at Initial Version
| Reported by: | Derek | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | 4.1 |
| Severity: | Normal | Keywords: | logging |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | yes | UI/UX: | no |
Description
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.
After a bit of searching, I have found this ticket below, which kind of summarises this behaviour.
https://code.djangoproject.com/ticket/33897
I think the documentation should say that once in production with Gunnicorn, there are no access logs with INFO status from the Django logger.
Note:
See TracTickets
for help on using tickets.