settings: Clean up pika logging.

It appears that a recent pika release started logging spammy INFO
output on the pika.connection and pika.channel channels, in addition
to the existing pika.adapters channel.

It's probably best to just move to WARNING-level logging for all of these.

This significantly cleans up the output when run-dev.py restarts
services due to a code change in the development environment.
This commit is contained in:
Tim Abbott
2020-05-07 11:55:11 -07:00
parent 73b2fcd618
commit e29d1fc776

View File

@@ -850,7 +850,7 @@ LOGGING: Dict[str, Any] = {
'handlers': ['console', 'ldap_file', 'errors_file'], 'handlers': ['console', 'ldap_file', 'errors_file'],
'propagate': False, 'propagate': False,
}, },
'pika.adapters': { 'pika': {
# pika is super chatty on INFO. # pika is super chatty on INFO.
'level': 'WARNING', 'level': 'WARNING',
# pika spews a lot of ERROR logs when a connection fails. # pika spews a lot of ERROR logs when a connection fails.
@@ -859,11 +859,6 @@ LOGGING: Dict[str, Any] = {
'handlers': ['console', 'file', 'errors_file'], 'handlers': ['console', 'file', 'errors_file'],
'propagate': False, 'propagate': False,
}, },
'pika.connection': {
# Leave `zulip_admins` out of the handlers. See pika.adapters above.
'handlers': ['console', 'file', 'errors_file'],
'propagate': False,
},
'requests': { 'requests': {
'level': 'WARNING', 'level': 'WARNING',
}, },