From Doug's comment on log.py it appears that the "oslo.<xxx>" format is the desired format.
The addition of "oslo_messaging" to the defaults appears to be a work around to oslo.messaging's inconsistent use of logging.
IMHO all oslo.<whatever> modules that have a dependency on oslo.log should use oslo.log for all logging. Using both oslo.log and py logging by the same module should be a bug (unless there's a specific use case requirement - like notification logging).
So if oslo.cache is using both oslo.log and py logging it should be fixed to use only oslo.log.
Adding in Doug who has more context on the oslo.log change.
Background:
The original bug: /bugs.launchpad .net/mos/ +bug/1484501
https:/
See Doug's comment here: /review. openstack. org/#/c/ 213795/ 2/oslo_ log/log. py
https:/
Looks like "oslo_messaging" was added to the defaults by this patch:
https:/ /review. openstack. org/#/c/ 458069/
From Doug's comment on log.py it appears that the "oslo.<xxx>" format is the desired format.
The addition of "oslo_messaging" to the defaults appears to be a work around to oslo.messaging's inconsistent use of logging.
IMHO all oslo.<whatever> modules that have a dependency on oslo.log should use oslo.log for all logging. Using both oslo.log and py logging by the same module should be a bug (unless there's a specific use case requirement - like notification logging).
So if oslo.cache is using both oslo.log and py logging it should be fixed to use only oslo.log.
Doug - what say ye?