5c2939f23b
Hard-coding watcher.openstack.common to warning level logging only makes it hard to debug watcher's interactions with other services, like when it's triggering and monitoring a server live migration. Since debug logging is controlled via the "debug" configuration option, we can just rely on that to filter out debug logs within watcher itself. Note this has been this way since change I699e0ab082657880998d8618fe29eb7f56c6c661 back in 2015 and there was no explanation why the watcher.openstack.common logging was set to WARN level. Change-Id: I939403a4ae36d1aa9ea83badb9404bc37d18a1a6 Related-Bug: #1828598
========================
Team and repository tags
========================
.. image:: https://governance.openstack.org/tc/badges/watcher.svg
:target: https://governance.openstack.org/tc/reference/tags/index.html
.. Change things from this point on
..
Except where otherwise noted, this document is licensed under Creative
Commons Attribution 3.0 License. You can view the license at:
https://creativecommons.org/licenses/by/3.0/
=======
Watcher
=======
OpenStack Watcher provides a flexible and scalable resource optimization
service for multi-tenant OpenStack-based clouds.
Watcher provides a robust framework to realize a wide range of cloud
optimization goals, including the reduction of data center
operating costs, increased system performance via intelligent virtual machine
migration, increased energy efficiency and more!
* Free software: Apache license
* Wiki: https://wiki.openstack.org/wiki/Watcher
* Source: https://opendev.org/openstack/watcher
* Bugs: https://bugs.launchpad.net/watcher
* Documentation: https://docs.openstack.org/watcher/latest/
* Release notes: https://docs.openstack.org/releasenotes/watcher/