gmane.comp.jakarta.log4j.user

Re: Programmatically setting log4j2 log level

Ralph Goers — 2013-05-19T06:06:47

Yes, that is correct.  The getRootLogger method is not included in the Configuration interface.  I created a unit test to verify the code worked and I should have pasted the code from the test.

Ralph

On May 18, 2013, at 7:26 PM, Eric Scheie wrote:

Re: Programmatically setting log4j2 log level

Eric Scheie — 2013-05-19T02:26:56

I should add that I didn't find the getRootLogger method in the API.  This
is the actual code I used.

  LoggerContext ctx = (LoggerContext) LogManager.getContext(false);

  Configuration config = ctx.getConfiguration();

  LoggerConfig loggerConfig = config.getLoggerConfig(LogManager.
ROOT_LOGGER_NAME);

  loggerConfig.setLevel(level);

  ctx.updateLoggers();


Thanks,

-Eric


On Sat, May 18, 2013 at 9:13 AM, Nick Williams <
nicholas< at >nicholaswilliams.net> wrote:

Re: Programmatically setting log4j2 log level

Nick Williams — 2013-05-18T16:13:03

I agree, Scott.

On May 18, 2013, at 11:11 AM, Scott Deboy wrote:

Re: Programmatically setting log4j2 log level

Scott Deboy — 2013-05-18T16:11:46

From looking at this, seems like config.getRootLoggerConfig() would be a
better name.
On May 17, 2013 10:40 PM, "Ralph Goers" <ralph.goers< at >dslextreme.com> wrote:

Re: Programmatically setting log4j2 log level

Eric Scheie — 2013-05-18T16:03:04

Thanks Ralph!  That was the code snippet I was looking for.  Works great!

Best,
-Eric


On Fri, May 17, 2013 at 10:39 PM, Ralph Goers <ralph.goers< at >dslextreme.com>wrote:

Re: Programmatically setting log4j2 log level

Ralph Goers — 2013-05-18T05:39:28

No, the X Logger does not inherit its level from the root Logger. It inherits its level from the root LoggerConfig.  See the picture at http://logging.apache.org/log4j/2.x/manual/architecture.html.

The level you are modifying is brought into each Logger so that the level can be tested very quickly.  That is why the note on the setLevel method says it is there primarily for unit testing. 

To do what you are attempting below you would need to do:

LoggerContext ctx = (LoggerContext) LogManager.getContext(false);
Configuration config = ctx.getConfiguration();
LoggerConfig loggerConfig = config.getRootLogger();
/* You could also specify the actual logger name as below and it will return the LoggerConfig used by the Logger.
    LoggerConfig loggerConfig = getLoggerConfig("X"); 
*/
loggerConfig.setLevel(Level.DEBUG);
ctx.updateLoggers();  // This causes all Loggers to refetch information from their LoggerConfig.

Ralph


On May 17, 2013, at 11:56 AM, Eric Scheie wrote:

Re: Programmatically setting log4j2 log level

Eric Scheie — 2013-05-17T18:56:20

Here is a simple program that can reproduce my problem:


import org.apache.logging.log4j.Level;
import org.apache.logging.log4j.LogManager;
import org.apache.logging.log4j.Logger;


public class Main
{
    public static void main(String[] args)
    {
        Logger rootLogger =
LogManager.getLogger(LogManager.ROOT_LOGGER_NAME);
        Logger xLogger = LogManager.getLogger("X");

        xLogger.info("This is an INFO log message.");


((org.apache.logging.log4j.core.Logger)rootLogger).setLevel(Level.DEBUG);

        rootLogger.debug("This is a debug message from ROOT.");
        xLogger.debug("This is a debug message from X.");
    }

}


log4j-api-2.0-beta5.jar and log4j-core-2.0-beta4.jar are the only jars on
the class path.  I'm using the same log4j2.xml file as above.


When I run this program, I see the following output:


2013-05-17 11:50:54,192 INFO  [main] {} Main.main(14) - This is an INFO log
message.

2013-05-17 11:50:54,194 DEBUG [main] {} Main.main(18) - This is a debug
message from ROOT.


The debug message from the X logger is missing.  Shouldn't the X logger be
inheriting the level from the Root Logger since an explicit level has not
been set?


Thanks,

-Eric




On Thu, May 16, 2013 at 11:49 PM, Ralph Goers <ralph.goers< at >dslextreme.com>wrote:

Re: Custom Syslog Format: Appending Exceptions?

Tomek Kaczynski — 2013-05-17T09:48:12

Hi Gary,

   I've found some time to commit my syslogWrapLayout class, but I can't
push my change to the server because it prompts me for a user and password.
As far as I see this is different account from the JIRA one. Can you please
help me and send me a link with guidline saying how to commit something to
the project ?

Tomek


On Wed, May 15, 2013 at 1:03 PM, Tomek Kaczynski
<tomek.kaczynski< at >gmail.com>wrote:

Re: Programmatically setting log4j2 log level

Ralph Goers — 2013-05-17T06:49:46

Can you provide a sample application that demonstrates this? 

Ralph

On May 16, 2013, at 9:44 PM, Eric Scheie wrote:

Programmatically setting log4j2 log level

Eric Scheie — 2013-05-17T04:44:40

I'm developing a web application and would like to be able to dynamically
change log levels from within my application instead of editing the log4j2
configuration file.   I'm using log4j 2.0 beta5.

I'm currently setting the log level after a form submit using:

((org.apache.logging.log4j.core.Logger) LogManager.getLogger(LogManager.
ROOT_LOGGER_NAME)).setLevel(Level.XXXXX);


And when I call:


((org.apache.logging.log4j.core.Logger) LogManager.getLogger(LogManager.
ROOT_LOGGER_NAME)).getLevel()


I get the level that I previously set as expected but I don't see the level
reflected in the logs.  For example, when changing the level to DEBUG on
the root logger I do not see debug messages written to the console.  If I
change the level of the root logger in my log4j2.xml configuration file I
do see the debug messages written to the console.


Here is my log4j2.xml file.


<?xml version="1.0" encoding="UTF-8"?>

<configuration status="DEBUG" monitorInterval="10">


    <appenders>

        <Console name="Console" target="SYSTEM_OUT">

            <PatternLayout pattern="%d %-5p [%t] %X %C{2}.%M(%L) - %m%n"/>

        </Console>

    </appenders>


    <loggers>

        <root level="INFO">

            <appender-ref ref="Console"/>

        </root>

    </loggers>

</configuration>


Any ideas I how I can change the root logger level after startup
programmtically?  I've been searching the web but the only things that come
up are related to log4j 1.2, I haven't found anything applicable to log4j
2.0.


Thanks,

-Eric

Re: Convient way to specify Log4J2 configuration outside of webapp?

Ralph Goers — 2013-05-16T01:11:18

No.  In that case see http://logging.apache.org/log4j/2.x/log4j-web/index.html and the Log4jContextListener.  https://svn.apache.org/repos/asf/logging/log4j/log4j2/trunk/samples/flume-remote/ has a sample web app that writes to Flume and uses the Log4jContextListener to locate its configuration.

Ralph


On May 15, 2013, at 12:57 PM, Jason B wrote:

Re: Convient way to specify Log4J2 configuration outside of webapp?

Jason B — 2013-05-15T19:57:41

Ran into another interesting use case:

Suppose I have two applications that run in the same Tomcat instance.  If I
use the -Dlog4j.configurationFile property, would I be able to specify
individual log configurations for those applications?


On Mon, May 13, 2013 at 12:13 PM, Jason B <makotothedragon< at >gmail.com> wrote:

Re: Custom Syslog Format: Appending Exceptions?

Tomek Kaczynski — 2013-05-15T11:03:20

Hi,
   The isssue is https://issues.apache.org/jira/browse/LOG4J2-256

    Whe should I put source and how ?
log4j2\core\src\main\java\org\apache\logging\log4j\core\layout is a good
location ?

Tomek



On Tue, May 14, 2013 at 9:48 PM, Jason B <makotothedragon< at >gmail.com> wrote:

Re: Adding appenders programatically

Te Ta — 2013-05-15T01:59:22

What is the recommended way of adding appenders in log4j 2.

In older version we were able to do
Logger.getLogger(theCategory).addAppender(appender).

Thanks!


On Tue, May 14, 2013 at 7:51 PM, Te Ta <ttashiuwyo< at >gmail.com> wrote:

Re: Custom Syslog Format: Appending Exceptions?

Jason B — 2013-05-14T19:48:39

I find this interesting...you had to go back a few levels to implement this
sort of custom behavior.  I'd love to see your patches, since I'm curious
if this can be incorporated into the SyslogAppender as opposed to going one
or two levels above it.

- Jason Black


On Tue, May 14, 2013 at 2:10 AM, Tomek Kaczynski
<tomek.kaczynski< at >gmail.com>wrote:

Burst Filter - Use to limit messages sent over a specific period?

Jason B — 2013-05-14T19:47:26

I'm attempting to leverage a burst filter in my application.  I wish to log
errors and send e-mails any time we log an error.  The main thing is, I
don't want to send more than a few e-mails in a given time period (say, one
per event per fifteen minutes), to avoid overwhelming my inbox with these
error events.

Burst Filter seems appropriate for this role, but the documentation is
lacking.  For instance:

 - If I want a filter to accept only those events that happen after the
threshold, but "rest" for that fifteen minute period of time, how would I
accomplish this?  The configuration is less than intuitive here.

 - What is the role of <TimeBasedTriggeringPolicy />? It's not mentioned
anywhere on the site, and only by digging in the source could I actually
determine what it's supposed to be doing.  It's also listed in every
example for filters on the site.

Thanks for clearing up any confusion.

- Jason Black

Re: Need help: Steps in your INSTALL doc failing

Mary Laude — 2013-05-14T17:52:09

This worked!  (see below)  Thanks to all.

Mary< at >WinServ2008-Enterprise /home/Mary/apache-log4j-1.2.17
$ java -cp ".;./log4j-1.2.17.jar" Hello
0 [main] DEBUG Hello  - Hello world.
0 [main] INFO Hello  - What a beatiful day.

Mary


On Tue, May 14, 2013 at 9:06 AM, Jacob Kjome <hoju< at >visi.com> wrote:

Re: Need help: Steps in your INSTALL doc failing

Jacob Kjome — 2013-05-14T16:06:08

Whoops, I neglected one thing...

java -cp .;log4j-1.2-17.jar Hello


Notice I added the current directory to the classpath.  Change the classpath 
separator character to a colon if needed.


Jake

On Tue, 14 May 2013 09:00:57 -0700
 Mary Laude <marylaudecissp< at >gmail.com> wrote:

Re: Need help: Steps in your INSTALL doc failing

Mary Laude — 2013-05-14T16:03:54

Also, if it helps, I've got jdk1.7.0_21 installed for java stuff.
Mary


On Tue, May 14, 2013 at 9:00 AM, Mary Laude <marylaudecissp< at >gmail.com>wrote:

Re: Need help: Steps in your INSTALL doc failing

JOSE L MARTINEZ-AVIAL — 2013-05-14T16:03:40

Assuming the package of Hello.class is the default package(so, no package)
the following should work:
$ java -cp .:./log4j-1.2.17.jar Hello



2013/5/14 Mary Laude <marylaudecissp< at >gmail.com>

Re: Need help: Steps in your INSTALL doc failing

Mary Laude — 2013-05-14T16:00:57

Here is what I just did.  Note I am actually inside a Win VM, at a cygwin
prompt.

Mary< at >WinServ2008-Enterprise /home/Mary/apache-log4j-1.2.17
$ ls
build.properties.sample  INSTALL       log4j-1.2.17.jar              site
build.xml                JarDir.class  NOTICE                        src
contribs                 JarDir.java   NTEventLogAppender.amd64.dll  tests
examples                 KEYS          NTEventLogAppender.dll
Hello.java               LICENSE       pom.xml

Mary< at >WinServ2008-Enterprise /home/Mary/apache-log4j-1.2.17
$ echo $CLASSPATH
/home/Mary/apache-log4j-1.2.17/

Mary< at >WinServ2008-Enterprise /home/Mary/apache-log4j-1.2.17
$ javac -cp ./log4j-1.2.17.jar Hello.java

Mary< at >WinServ2008-Enterprise /home/Mary/apache-log4j-1.2.17
$ java -cp ./log4j-1.2.17.jar Hello
Error: Could not find or load main class Hello

Mary< at >WinServ2008-Enterprise /home/Mary/apache-log4j-1.2.17
$ ls
build.properties.sample  Hello.java    LICENSE                       pom.xml
build.xml                INSTALL       log4j-1.2.17.jar              site
contribs                 JarDir.class  NOTICE                        src
examples                 JarDir.java   NTEventLogAppender.amd64.dll  tests
Hello.class              KEYS          NTEventLogAppender.dll


Any ideas?
Thx.
Mary


On Tue, May 14, 2013 at 8:36 AM, Jacob Kjome <hoju< at >visi.com> wrote: