logger: disable state logging by default

[ghost]

• Use different levels of verbosity as suggested by this comment: logger: disable state logging by default #2332 (comment)

• Add a TRACE level to the logging module

• Change logger.debug(x) -> logger.log(TRACE, x)

Related: #2329

[casperdcl]

perhaps creating & using logging.TRACE = 5 is better than this env var?

[ghost]

@casperdcl could you explain a little bit more? I'm not sure where the user should set the logging.TRACE = 5 is it through the config file?

[casperdcl]

cmd	level
default	INFO
-v	DEBUG
-vv	TRACE

[ghost]

Ohh got it 👍 yep, that's what I purposed first on the linked issue:

My suggestion would be to create different verbose levels, -vvv (INFO, DEBUG, DATABASE?)
...
Modify the -v so you can express the level of verbosity with several ones -vvv
#2329 (comment)

I like this idea better instead of using the env var

[casperdcl]

though really I'd prefer --log TRACE|DEBUG|INFO|WARN(ING)|ERROR|FATAL, and for backward compatibility -v is a shortcut for --log DEBUG

[ghost]

@casperdcl is this more common? I'm more used to the v's 😅

Even the argparse documentation has a section on it:

>>> parser = argparse.ArgumentParser()
>>> parser.add_argument('--verbose', '-v', action='count')
>>> parser.parse_args(['-vvv'])
Namespace(verbose=3)

[casperdcl]

the problem with counting -v is there's no way to access WARN and ERROR. We could count -q (quiet) or similar for that.

[ghost]

@casperdcl so, it would start on INFO by deafult, if you want just warnings then use one -q, if you want to silence everything -qq, and one -v will be for DEBUG and two for TRACE, right?

🤔 let's wait for the opinion of @shcheklein, @efiop , @Suor , @pared (need some quorum on this one, can't decide by myself)

[Suor]

I am ok with counting v/qs, this is more friendly for typing in. --log might be useful for scripting - more obvious when you read it, not sure how much common scripting dvc is though.

So my preference: implement v/qs, and keep --log up our sleeves for now.

[ghost]

Awesome, @Suor , I'll add those implementation details to the description.