According to mvnrepository, logback^[1] is the most popular Java logging framework^[2]. It is the successor^[3] of log4j 1.x and is very similar conceptually to log4j 1.x as both frameworks were developed by the same person, namely Ceki Gülcü.

The main difference between log4j 1.x and logback is that logback implements the SLF4J API^[4] natively. In addition, logback has a larger battery of tests and more extensive documentation.^[5]

Modules

Logback ships with three modules. The logback-classic module which is the equivalent of log4j 1.x. The logback-access module can be integrated with web-container to log HTTP traffic. The logback-core module provides common functionality required by the previous two modules.

Dependencies

For Maven users, you can declare logback-classic as a dependency in the pom.xml file of your project.

<dependency>
    <groupId>ch.qos.logback</groupId>
    <artifactId>logback-classic</artifactId>
    <version>1.4.4</version>
</dependency>

The transitive dependencies logback-core and slf4j-api will pulled in by Maven automatically.

Architecture of logback-classic

Logback-classic is based on logback-core and natively implements the SLF4J API. Logging is initiated by calling the printing methods of a logger^[6] instance.

logger.debug("Hello world");

Loggers are obtained by calling the getLogger()^[7] method of LoggerFactory^[8] class.

Logger logger = LoggerFactory.getLogger(HelloWorld.class);

Configuration

Logback offers very powerful configuration options which are too numerous to detail here.

Here is a sample configuration file that logs to the console.

<configuration>
  <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
    <encoder>
      <pattern>%d [%thread] %-5level %logger{36} - %msg%n</pattern>
    </encoder>
  </appender>

  <root level="info">
    <appender-ref ref="STDOUT" />
  </root>
</configuration>

References