JBoss Logging

jboss log

WildFly provides an highly-configurable logging subsystem that can be used both by WildFly core and by applications. The logging subsystem is based on JBoss LogManager project which supports several logging frameworks that you can configure on the top of JBoss Logging.

To learn more about JBoss Logging we recommend the following articles:

Internal Logging

Configuring a Periodic Rotating File Handler

Configuring Handlers for single packages

Configuring Logging for a single application

How to enable debug logs

How to read WildFly log files using the CLI

5 WildFly Loggers you should know about

Log4j Configuration

How to fix Log4j CVE-2021-44228

Configuring Log4j1 in your applications

Configuring Log4j2 in your applications

Configure Log4j in an EAR file

How to print logs in JSON format in WildFly

by

This article discusses the configuration you can apply in WildFly to enable logging in JSON format. We will learn how to do that natively in WildFly or using a Log4j custom configuration. Strategies for logging in JSON There are several use cases in which logging in JSON format can be useful. For example: Use cases … Read more

How to compress logs in WildFly

by

This article shows how to enable logs compression in WildFly by setting the appropriate suffix in your Periodic Rotating File Handler. In the second part of this tutorial we will learn how to compress logs using Log4j instead.

Read more

How to configure SLF4J in WildFly applications

by

In this tutorial, we will discuss how to use Simple Logging Facade for Java (SLF4J) with Wildfly application server. SLF4J is a logging facade that provides a unified interface for various logging frameworks, such as log4j, java.util.logging, and Logback. It allows for the decoupling of the application code from the underlying logging framework, making it easier to change the logging framework without modifying the application code.

Read more

Getting Started with Simple Logging Facade (SLF4J)

by

Simple Logging Facade for Java (SLF4J) is a logging facade that provides a unified interface for various logging frameworks, such as log4j, java.util.logging, and Logback. It allows for the decoupling of the application code from the underlying logging framework, making it easier to change the logging framework without modifying the application code. Here is a small tutorial to discuss the advantages of using SLF4J versus direct logging configuration.

Read more

How to fix Log4j CVE-2021-44228

by

This security bulletin discusses the recent flaws in Log4j2 library which affects some recent versions of this opensource library. Let’s see how to perform checks and mitigation actions if your Java applications are using a flawed Log4j2 version.

Read more

Where are JBoss logs located?

by

We will shortly discuss where JBoss EAP / WildFly logs are located. The location of JBoss logs basically depends on which mode you are using to start the application server. View logs in standalone mode When running in standalone mode, JBoss logs are located in the standalone/log folder: As you can see, the currently running … Read more