Vfrdtyky

I would like to have a piece of code that would ONLY save ALL(Or just the ERROR logs) from the log4j to a file. All the solutions that I found and tried are still showing information in the console, which I don't want to.
I tried this piece of code:

public static void configureLogging(String fileName) {

    ConfigurationBuilder<BuiltConfiguration> builder = ConfigurationBuilderFactory.newConfigurationBuilder();

    builder.setStatusLevel(Level.ALL);

    LayoutComponentBuilder layoutBuilder = builder.newLayout("PatternLayout").addAttribute("pattern", "%d [%t] %-5level: %msg%n%throwable");



    ComponentBuilder triggeringPolicies = builder.newComponent("Policies")

            .addComponent(builder.newComponent("CronTriggeringPolicy")

                    .addAttribute("schedule", "0 0 0 * * ?"))

            .addComponent(builder.newComponent("SizeBasedTriggeringPolicy")

                    .addAttribute("size", "100M"));



    AppenderComponentBuilder rollingFile

            = builder.newAppender("rolling", "RollingFile").add(layoutBuilder);

    rollingFile.addAttribute("fileName", fileName + ".log");

    rollingFile.addAttribute("filePattern", fileName + "-%d{MM-dd-yy}.log.gz");

    rollingFile.addComponent(triggeringPolicies);



    builder.add(rollingFile);

    builder.add(builder.newRootLogger(Level.ALL).add(builder.newAppenderRef("rolling")));

    builder.setConfigurationName("BuilderTest");



    Configurator.initialize(builder.build());

}

but I'm seeing everything in the console terminal:

2018-11-16 11:24:42,884 main DEBUG Apache Log4j Core 2.11.1 initializing configuration org.apache.logging.log4j.core.config.builder.impl.BuiltConfiguration@3b0143d3

2018-11-16 11:24:42,887 main DEBUG Installed 1 script engine

2018-11-16 11:24:43,166 main DEBUG Oracle Nashorn version: 1.8.0_144, language: ECMAScript, threading: Not Thread Safe, compile: true, names: [nashorn, Nashorn, js, JS, JavaScript, javascript, ECMAScript, ecmascript], factory class: jdk.nashorn.api.scripting.NashornScriptEngineFactory

2018-11-16 11:24:43,166 main DEBUG PluginManager 'Core' found 117 plugins

2018-11-16 11:24:43,166 main DEBUG PluginManager 'Level' found 0 plugins

2018-11-16 11:24:43,168 main DEBUG PluginManager 'Lookup' found 13 plugins

2018-11-16 11:24:43,168 main DEBUG Building Plugin[name=AppenderRef, class=org.apache.logging.log4j.core.config.AppenderRef].

2018-11-16 11:24:43,170 main DEBUG createAppenderRef(ref="rolling", level="null", Filter=null)

2018-11-16 11:24:43,170 main DEBUG Building Plugin[name=root, class=org.apache.logging.log4j.core.config.LoggerConfig$RootLogger].

2018-11-16 11:24:43,173 main DEBUG createLogger(additivity="null", level="ALL", includeLocation="null", ={rolling}, ={}, Configuration(BuilderTest), Filter=null)

2018-11-16 11:24:43,174 main DEBUG Building Plugin[name=loggers, class=org.apache.logging.log4j.core.config.LoggersPlugin].

Could anyone explain what is wrong with my approach?

Many Thanks,
Joao

Without more details it's hard to give an exact answer, however, I will try to help point you in the right direction.

First, I would highly recommend that you do not use programmatic configuration unless you have a very good reason to do so. Log4j2 provides some very nice features that make it possible to do almost everything via a configuration file.

My best guess is that you want to use a dynamic file name that is somehow selected at runtime. If this is the case you can definitely do this using log4j2 lookups. In another answer I wrote an example that uses the system properties lookup. As you can see the file name is dynamic based on a system property rather than being static or hardcoded into the config file. There are many other lookups, so I suggest reading the manual carefully and choosing one that best fits your needs.

As for your question of how to send all logs to a file it's as simple as not specifying a console appender. As stated in the log4j2 manual:

Appenders are responsible for delivering LogEvents to their
destination.

Referring again to the other answer I wrote you'll also notice that the configuration does not use console appender and thus does not generate any console messages.

Since I do not see you creating a console appender I'm betting that the issue is the following: builder.setStatusLevel(Level.ALL);

This would appear to be setting the log4j2 status logger to a level of "ALL" meaning it's going to generate all of the internal log4j2 log messages. I would recommend using a level of "WARN" or "ERROR" but if you really want to make sure that messages are never sent to console you could set this to "OFF".