I wouldn’t be opposed to having a “TRACE” that is even lower than DEBUG that we could use for tracing paths during debug. Adding an additional unconventional logging level is not unheard of but it would mean having a non-standard wrapper
around the logging library. Not unheard-of and doable without much fuss.
All,
Python includes the following logging level
5 CRITICAL or FATAL
4 ERROR
3 WARNING or WARN
2 INFO
1 DEBUG
The lower the number the more logging you get. Currently in Monolithic volttron (VOLTTRON/volttron) on github when you start the platform with one –verbose then you get info level, two –verbose –verbose or (-vv) you get debug level.
With a production system, I would like to be able to run in WARN or ERROR mode to the main log file and potentially have a DEBUG log that rotates on a daily or more frequent nature.
For active debugging I would still use DEBUG, but could run the platform in INFO and then run the agents in DEBUG mode.
So the long and the short of it.
Do you think volttron -v should be info or error? With each additional -v getting more and more output?
I think this will help us better provide better message distinctions. Please respond so that I know if this is an issue with your current platforms or not.
Thanks
Craig