Django logging requests

懵懂的女人 提交于 2020-01-30 05:07:09

问题


I'm using django 1.11 in aws elastic beanstalk and I've been trying to get my app to log with no luck . . .

I have these in my settings.py

LOGGING_CONFIG = None
LOGGING = {
    'version': 1,
    'disable_existing_loggers': False,
    'handlers': {
        'file': {
            'level': 'DEBUG',
            'class': 'logging.FileHandler',
            'filename': '/opt/python/current/app/staging.log',
        },
    },
    'loggers': {
        '': {
            'handlers': ['file'],
            'level': 'DEBUG',
            'propagate': True,
        },
        'django': {
            'handlers': ['file'],
            'level': 'DEBUG',
            'propagate': True,
        },
        'django.request': {
            'handlers': ['file'],
            'level': 'DEBUG',
            'propagate': True,
        },
    },
}
import logging.config
logging.config.dictConfig(LOGGING)

then I try to call one of my API and expecting something would show up in the log but it didn't. I django.request logger supposed to automatically log all incoming request or do I have to create a middleware that does logger.debug('something')?

logging in django is a lot more complicated than I thought :(


回答1:


demo of logging in django,log is location in /path/to/your/project/log/info.log, your need to create info.log in log/ dir first.

settings.py

LOG_PATH = os.path.join(BASE_DIR, "log/")
LOGGING = {
    'version': 1,
    'disable_existing_loggers': True,
    'formatters': {
        'standard': {
            'format': '%(asctime)s [%(levelname)s]- %(message)s'}

    },
    'handlers': {
        'django_error': {
            'level': 'DEBUG',
            'class': 'logging.handlers.RotatingFileHandler',
            'filename': LOG_PATH + 'django.log',
            'formatter': 'standard'
        },
        'info': {
            'level': 'DEBUG',
            'class': 'logging.handlers.RotatingFileHandler',
            'filename': LOG_PATH + 'info.log',
            'formatter': 'standard'
        },
        'console': {
            'level': 'DEBUG',
            'class': 'logging.StreamHandler',
            'formatter': 'standard'
        }
    },
    'loggers': {
        'info': {
            'handlers': ['info', "console"],
            'level': 'DEBUG',
            'propagate': True
        },
        'django': {
            'handlers': ['console'],
            'level': 'INFO',
            'propagate': True,
        },
        'django.request': {
            'handlers': ['django_error', 'console'],
            'level': 'DEBUG',
            'propagate': True,
        },
        'django.db.backends': {
            'handlers': ['console'],
            'level': 'ERROR',
            'propagate': True,
        }
    },
}

the effect of loggers is:

  • info: your custom debug info
  • django: the request record
  • django.request: the error request
  • django.db.backends:Messages relating to the interaction of code with the database

more info here

views.py

import logging
logger = logging.getLogger("info")
logger.info('something')

you will get

2017-08-31 13:05:40,492 [INFO]- something

in log/info.log later.




回答2:


Django logger extensions work differently in development than in production (settings.DEBUG=True|False).

What you expect to see - http request logs - are written by django.server logger,
which is active only in development server (runserver command).

I see that in your configuration you use django.request logger. This logger name is very confusing - because as its name suggest - users will expect it to log all http requests - but it won't.

django.request will log only 4xx and 5xx requests.

I've made a screencast which explain this issue in detail.

Django documentation about loggers.



来源:https://stackoverflow.com/questions/45972977/django-logging-requests

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!