Logging in Java: Overview of Best Libraries and Solutions

Logging for Java: Best Solutions

Logging is an essential part of developing any serious Java application. It helps track code execution, identify errors, conduct audits, and analyze system behavior in production. In this article, we will review the main logging libraries for Java, their features, advantages and disadvantages, and provide practical code examples.

Why is logging needed?

Properly configured logging allows you to:

• Quickly find and fix errors;
• Collect application performance statistics;
• Maintain a security log;
• Provide monitoring and alerting;
• Analyze performance.

Main Logging Libraries

1. java.util.logging (JUL)

Built-in JDK library. Simple but limited. Suitable for small projects or rapid prototyping.

import java.util.logging.Logger;import java.util.logging.Level;

public class JULExample {    private static final Logger logger = Logger.getLogger(JULExample.class.getName());

    public static void main(String[] args) {        logger.info("Application started");        logger.warning("Warning: low memory");        try {            throw new Exception("Test error");        } catch (Exception e) {            logger.log(Level.SEVERE, "An error occurred", e);        }    }}

Cons: no support for modern formats, weak performance, lack of flexible configuration.

2. Log4j 2

A popular and powerful library from Apache. Supports asynchronous logging, multiple appenders (files, databases, networks) and filters.

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

public class Log4j2Example {    private static final Logger logger = LogManager.getLogger(Log4j2Example.class);

    public static void main(String[] args) {        logger.debug("Debug message");        logger.info("Informational message");        logger.error("Critical error: {}", "division by zero");    }}

Pros: high performance, support for asynchronous loggers, rich configuration (XML, JSON, YAML).

Configuration (log4j2.xml):

<?xml version="1.0" encoding="UTF-8"?><Configuration status="WARN">    <Appenders>        <Console name="Console" target="SYSTEM_OUT">            <PatternLayout pattern="%d{HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n"/>        </Console>    </Appenders>    <Loggers>        <Root level="info">            <AppenderRef ref="Console"/>        </Root>    </Loggers></Configuration>

3. Logback

Succeeded Log4j 1.x. It is the default implementation of SLF4J. Known for high speed and flexibility.

import org.slf4j.Logger;import org.slf4j.LoggerFactory;

public class LogbackExample {    private static final Logger logger = LoggerFactory.getLogger(LogbackExample.class);

    public static void main(String[] args) {        logger.trace("Trace message (usually not output)");        logger.debug("Debug: value x = {}", 42);        logger.info("Application ready to work");        logger.warn("Warning: response time exceeds limit");        logger.error("Database connection error", new RuntimeException("Connection refused"));    }}

Configuration (logback.xml):

<configuration>    <appender name="FILE" class="ch.qos.logback.core.FileAppender">        <file>logs/app.log</file>        <encoder>            <pattern>%date %level [%thread] %logger{10} [%file: