Skip to main content

Getting Started With Log4j Logging

Introduction

For Java applications, Log4j is a commonly used and trusted logging tool.
When an application is deployed to an application server, logging is a must-have feature.

In this tutorial, we'll see how to set up Log4j for a simple Java application.

You can find all code related to this tutorial inside GitHub project.


Why do we need Logging

Logging is an important part of the application since it records user actions, input requests and output responses, error messages, and more.

This information aids in the understanding of the application both inside and outside of it, as well as providing faster feedback or support for any issues that may occur during the application's execution.


Maven configuration

Add following dependencies into pom.xml

pom.xml

<dependencies>
    <dependency>
        <groupId>org.apache.logging.log4j</groupId>
        <artifactId>log4j-api</artifactId>
        <version>2.17.2</version>
    </dependency>
    <dependency>
        <groupId>org.apache.logging.log4j</groupId>
        <artifactId>log4j-core</artifactId>
        <version>2.17.2</version>
    </dependency>
</dependencies>


Note: Choose the latest version of Log4J to guard against any unwanted vulnerabilities. 


Sample code

Now lets add few log message and see the result

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

public class MainApp {

    public static void main(String[] args) {
        Logger logger = LogManager.getLogger();
        printLoggingLevels(logger);
    }

    private static void printLoggingLevels(Logger logger) {
        logger.trace("logging trace level");
        logger.debug("logging debug level");
        logger.info("logging info level");
        logger.warn("logging warn level");
        logger.error("logging error level");
        logger.fatal("logging fatal level");
    }
}


Logging levels

All of the logging levels available in the Log4j package are demonstrated in the code sample above.

Let's look at what each level does.

  • Trace : A fine-grained message that records all traces of the application's flow.
  • Debug : Messages used to debug an application's behaviour during development.
  • Info : Common application flow message.
  • Warn : An event that may result in an error.
  • Error : An exception occurred within the application, which may be recovered.
  • Fatal : An application encounters an error that cannot be recovered from.


When we execute the application, Log4J starts logging into the console.

02:34:02.491 [main] ERROR com.zainabed.tutorials.logging.MainApp - logging error level
02:34:02.504 [main] FATAL com.zainabed.tutorials.logging.MainApp - logging fatal level


As we can see it logs only Error & Fatal level messages only.

This happens because of Logging level filtering 


Logging level filter

Log4j has the following filter mechanism.

All <  Trace < Debug < Info < Warn < Error < Fatal

If the logging level is set to be info, then only info, warning, error, and fatal messages will be logged into the console.

When the logging level is set to "Error," both the Error and Fatal messages are displayed.

The default logging level is Error for applications. That is why we see only Error and Fatal log messages.

To override the default behavior, we need to add the Log4j2.xml configuration file and provide an appropriate logging level to log relevant messages.


Conclusion

Every application requires a logging method to record the flow and behaviour of the application.
Log4j is a widely adopted tool to provide such a facility.

Log4j is extremely configurable, and application-specific parameters are set via Log4j2.xml.



Comments

Subscribe for latest tutorial updates

* indicates required

Popular posts from this blog

Preload Images Using Javascript

Preload Image is technique which helps browser to render images with minimum delay. Today we will see example of image gallery. Gallery contain 5 images which load images one after another whenever user clicks next and back button. This is a basic image gallery scenario which is used in all possible website, then why we need preloaded images for this gallery? Now a day’s most of website becoming faster and user expectation is increasing. Suppose your website doesn’t use preload image technique for gallery and a user visits any image gallery from Google Plus or Facebook and visits your website gallery. Then that user always prefer those websites rather than yours. Why? Because your website load one image at a time. When user click on next button, then only gallery load image and user has wait till it get loaded. To avoid this situation gallery needs to download all images ...

CSS: How To Create Custom Scrollbar For Webkit Supported Browsers

In this tutorial, we will learn how to create a custom scroll bar using custom CSS styles. Custom scrollbars are becoming increasingly popular, and I'm excited to learn more about them. A scrollbar can be customised for a variety of reasons. The default scrollbar, for example, can make an app's UI look inconsistent across various versions of windows, thus we can benefit from having a single style here. This tutorial will help to create a custom scrollbar. Let's see how One of the most interesting aspects of these scrollbars is that they may be rendered in a variety of styles for different HTML elements on the same webpage. We will see the implementation of such a scrollbar for Webkit-supported browsers. First we will look at the basic CSS properties of the scrollbar. ::-webkit-scrollbar              ::-webkit-scrollbar-thumb        ::-webkit-scrollbar-track  ...

How to enable SQL logs in Spring Boot application?

This tutorial will demonstrate how to enable and disable SQL log statements in a Spring Boot application in order to debug SQL flow. Problem You will frequently need to debug the SQL statement while developing a Spring Boot application with a SQL database. SQL debug logs can assist you figure out what's wrong with JPA statements and whether or not there's a problem with database connectivity. Example  If you've built custom Spring data JPA methods and need to know what SQL statement is being utilized behind them, return repository . findByUsernameIn ( usernames ); Then you can enable Hibernet debug mode to log SQL statements. Solution Update the application.yml file with the Hibernet configuration as logging: level: org: hibernate: DEBUG or application.properties as logging.level.org.hibernate=DEBUG The SQL statement will appear in the application logs after modifying the configuration file and restarting the application. 2022-04-07 08:41...