3👍
✅
You need to specify filters
:
'loggers': {
'django': {
'handlers':['console'],
'filters': [], # <-- this line
'propagate': True,
'level':'INFO',
},
},
I don’t know why.
2👍
Logger level has higher priority to handler level,
logging.DEBUG has value 10, and logging.INFO has value 20.
'handlers': {
'console': {
'level':'DEBUG',
},
}
'loggers': {
'level':'INFO',
}
Hence your logging is always set at INFO level coz of logger priority, and DEBUG output will not be used.
this is what i feels is the issue.
- [Django]-Populate() isn't reentrant Django Google App Engine
- [Django]-Django Crispy Forms and Option Groups
- [Django]-Django problem with extends template tag
0👍
Took me a while to dig out, but it’s because of this:
https://docs.djangoproject.com/en/dev/releases/1.4/#request-exceptions-are-now-always-logged
It’s quite confusing and should be highlighted in the logs documentation, which it isn’t.
- [Django]-Django: Views: class vs function
- [Django]-Django problem with extends template tag
- [Django]-How can I resolve this linting error? "Consider adding meta keywords. <html lang="en-US"> (H031)"
Source:stackexchange.com