openstack/ironic
Code Issues Proposed changes

Set lockutils default logging

Browse Source 
While developing some internal metrics collection capability,
and the realization that a lock was needed, we realized that
the lock activity itself would be a bit noisy. And image actions
also get lock logging, and it is just really noisy, but not super
helpful for troubleshooting.

So, set it to WARNING instead.

Discussion wise, see:
https://review.opendev.org/c/openstack/ironic-lib/+/865311

Change-Id: I3ab14ee5b5cc063784d26e3c760f1422c692060d
This commit is contained in:
Julia Kreger 2023-02-02 15:50:28 -08:00
parent 4704c74b4d
commit e32d1ac7a2
2 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
ironic/conf/opts.py
View File

@ -89,5 +89,8 @@ def update_opt_defaults():
'openstack=WARNING',
# Policy logging is not necessarily useless, but very verbose
'oslo_policy=WARNING',
# Concurrency lock logging is not bad, but exceptionally noisy
# and typically not needed in debugging Ironic itself.
'oslo_concurrency.lockutils=WARNING',
]
)

8
releasenotes/notes/lockutils-default-logging-8c38b8c0ac71043f.yaml Normal file
View File

@ -0,0 +1,8 @@
---
other:
- |
The default logging level for the ``oslo_concurrencty.lockutils``
module logging has been changed to ``WARNING``. By default, the debug
logging was resulting in lots of noise. Operators wishing to view debug
logging for this module can tuilize the ``[DEFAULT]default_log_levels``
configuration option.