On Mon, Jan 22, 2018 at 12:15 PM, Matt Sicker <boa...@gmail.com> wrote:
> There are some related properties to what you're proposing already: > > log4j2.simplelogStatusLoggerLevel > log4j2.defaultStatusLevel > log4j2.statusLoggerLevel > > Though it's a bit confusing setting them here since some of these > properties get overridden by the configuration file or only apply in > certain life cycles. > > Are you proposing a unified property that overrides everything globally? Or > would the status attribute of the configuration element take precedence? > Yikes. What I want to do is use a -D on the command line instead of editing the status attribute in an XML configuration file. The docs for log4j2.defaultStatusLevel and log4j2.statusLoggerLevel are very confusing IMO. I suppose I'll have to try both. Can these docs be improved with an intro sentence for each saying "To do X, use Y"? Gary > > On 21 January 2018 at 13:53, Gary Gregory <garydgreg...@gmail.com> wrote: > > > Hi All, > > > > I want to toggle between different status levels on the command line > > and log4j2.debug can't do that. > > > > How about adding log4j2.status=level ? > > > > Gary > > > > > > -- > Matt Sicker <boa...@gmail.com> >
