+1 to making the change and updating the docs to reflect only the new log levels.
On Wed, Mar 15, 2017 at 10:45 AM Jinmei Liao <jil...@pivotal.io> wrote: > Hi, all, > > Geode, before using log4j for logging has implemented its own LogWriters > and logLevels. Geode log levels has values like "finest, finer, fine, > config, info, warning, error, severe". We've moved away from using these > log writers to favor using log4j logging. So, mostly, geode logs have log4j > log statements with levels like "fatal, error, warn, info, debug". > > But by examining our existing commands that has log-level options, > specifically "start server", "start locator", "alter runtime", "change > log-level", these commands are still accepting log-levels with geode log > levels, and under the cover, it has a mapping to the log4j levels. Since we > are moving away from geode's own logging, I would like to propose changing > these commands to use log4j log levels explicitly. > > To avoid breaking existing commands, we can provide a mapping to the log4j > levels after user provides an "old" log level, but at least I would like to > have the auto complete start showing the log4j levels instead of the geode > log levels and move towards getting rid of these old levels completely. > > -- > Cheers > > Jinmei >
