Many things are logged as info that belong more in the category of debug information. This issue should be updated with more specifics when they are understood (what should be logged to info?) and referenced in pull requests on a campfire principle basis, i.e. logging statements are updated when code in proximity is touched.
This will make debugging easier such that we can increase the granularity of information when it is needed rather than be flooded with statements by default.
Yes the usage of loggingis inconsistent, and need a cleanup. It might be an idea to first agree on principles, and perhaps first outline those principles under the "Contribution" part in the docs.
Many things are logged as
info
that belong more in the category ofdebug
information. This issue should be updated with more specifics when they are understood (what should be logged to info?) and referenced in pull requests on a campfire principle basis, i.e. logging statements are updated when code in proximity is touched.This will make debugging easier such that we can increase the granularity of information when it is needed rather than be flooded with statements by default.