Describe the bug
At the moment, we are using the INFO, ERROR and CRITICAL codes from logger but we need to be clearer about the audience for different messages and target them better.
The key one here at the moment is that we are using INFO for all sorts of internal setup things (like the various function registries). Those are not messages that a normal user will want to see - they make much more sense as DEBUG messages - and we can add a debug or log_level item to the config (defaulting to INFO) that allows them to be exposed. Developers can of course programatically change the logging level.
We also have WARNING - which I don't think is used yet. This should also be for user focussed messages. We can create custom levels, but I don't see any need at present.
Describe the bug
At the moment, we are using the INFO, ERROR and CRITICAL codes from
loggerbut we need to be clearer about the audience for different messages and target them better.The key one here at the moment is that we are using INFO for all sorts of internal setup things (like the various function registries). Those are not messages that a normal user will want to see - they make much more sense as DEBUG messages - and we can add a
debugorlog_levelitem to the config (defaulting to INFO) that allows them to be exposed. Developers can of course programatically change the logging level.We also have WARNING - which I don't think is used yet. This should also be for user focussed messages. We can create custom levels, but I don't see any need at present.