Hi,

I’ve just tried setting everything to warn through the nova.conf option default_log_levels, as suggested. However, I’m still getting info level logs from the resource tracker like this :

INFO nova.compute.resource_tracker

Could the compute resource tracker logs be managed by another parameter than what’s in the default list for that configuration option?

Best regards,

Jean-Philippe Méthot

Openstack system administrator

Administrateur système Openstack

PlanetHoster inc.

Le 7 mai 2019 à 09:02, Jay Pipes <jaypipes@gmail.com> a écrit :

On 05/06/2019 05:56 PM, Jean-Philippe Méthot wrote:

Hi,
We’ve been modifying our login habits for Nova on our Openstack setup to try to send only warning level and up logs to our log servers. To do so, I’ve created a logging.conf and configured logging according to the logging module documentation. While what I’ve done works, it seems to be a very convoluted process for something as simple as changing the logging level to warning. We worry that if we upgrade and the syntax for this configuration file changes, we may have to push more changes through ansible than we would like to.

It's unlikely that the syntax for the logging configuration file will change since it's upstream Python, not OpenStack or Nova that is the source of this syntax.

That said, if all you want to do is change some or all package default logging levels, you can change the value of the CONF.default_log_levels option.

The default_log_levels CONF option is actually derived from the oslo_log package that is used by all OpenStack service projects. It's default value is here:

https://github.com/openstack/oslo.log/blob/29671ef2bfacb416d397abc57170bb090b116f68/oslo_log/_options.py#L19-L31

So, if you don't want to mess with the standard Python logging conf, you can just change that CONF.default_log_levels option. Note that if you do specify a logging config file using a non-None CONF.log_config_append value, then all other logging configuration options (like default_log_levels) are ignored).

Best,
-jay