Скачать или смотреть Excluding the io.undertow.request Package from Logging in WildFly

A step-by-step guide to exclude the `io.undertow.request` package from logging in WildFly, ensuring your logs are cleaner and more relevant.
---
This video is based on the question https://stackoverflow.com/q/67496728/ asked by the user 'Chamod Pathirana' ( https://stackoverflow.com/u/6874531/ ) and on the answer https://stackoverflow.com/a/67501242/ provided by the user 'Abhijit Humbe' ( https://stackoverflow.com/u/5901697/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: How to exclude io.undertow.request package from the logging in wildfly

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
How to Exclude the io.undertow.request Package from Logging in WildFly

When managing a WildFly server, you may encounter various error logs that can clutter your logging output. One such common issue arises from the io.undertow.request package, where logs related to errors like "Broken pipe" can become frequent and frustrating. This situation creates the necessity for a clean logging environment, especially for developers and system administrators who need to focus on more critical issues without the distraction of repetitive error messages.

Fortunately, there's a straightforward way to exclude the io.undertow.request package from your logging configurations in WildFly. In this guide, we will walk you through the steps to modify your standalone-*.xml configuration file to achieve precisely that.

Understanding the Problem

Why Exclude io.undertow.request Logs?

The io.undertow.request package often generates logs related to network communications, specifically errors that do not typically require immediate attention for application developers. By excluding these logs, the server logs can remain clear of noise, allowing for easier identification of relevant warnings and errors that matter more.

Solution: Modifying the Logging Configuration

You can easily configure WildFly to stop logging messages from the io.undertow.request package by following these simple steps:

Step 1: Locate the Configuration File

First, you need to locate the standalone-*.xml configuration file in your WildFly installation directory. This file is typically found in the standalone/configuration folder.

Step 2: Open the Configuration File

Use a text editor to open the standalone-*.xml file. Always make a backup of your configuration file before making any changes, in case you need to revert to the original settings.

Step 3: Update the Logging Subsystem

Within the configuration file, locate the <logging> subsystem. You will add a new logger entry specifically for the io.undertow.request package.

Insert the following lines of code into the <logging> section:

[[See Video to Reveal this Text or Code Snippet]]

Step 4: Save Your Changes

After adding the logger configuration, save the file and close your text editor.

Step 5: Restart WildFly

To apply your changes, restart your WildFly server. You can do this through the command line or your preferred method.

Conclusion

By following these steps, you will successfully exclude the io.undertow.request package from logging in WildFly. This change will help in reducing log clutter, allowing you to focus on the issues that truly matter to the performance of your application.

Feel free to share your experiences or any questions regarding this process in the comments below. Happy logging!