Скачать или смотреть How to Print Info Logs Only to Console and Info, Debug, and Errors to File Using Logback

Learn how to configure Logback to direct `INFO` logs to the console while sending `INFO`, `DEBUG`, and `ERROR` logs to a file. Follow our step-by-step guide for effective logging management.
---
This video is based on the question https://stackoverflow.com/q/74838918/ asked by the user 'ramkumar-yoganathan' ( https://stackoverflow.com/u/6703119/ ) and on the answer https://stackoverflow.com/a/75391137/ provided by the user 'Manish' ( https://stackoverflow.com/u/3041326/ ) 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 do I print info logs only to console and info, debug and errors to file using logback?

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 Print Info Logs Only to Console and Info, Debug, and Errors to File Using Logback

Logback is a highly configurable logging framework that allows developers to manage how logs are displayed. One of the common requests when using Logback is to configure log levels so that certain messages are directed to specific outputs. In this guide, we'll explore how to print INFO logs only to the console while directing INFO, DEBUG, and ERROR logs to a file.

Understanding Your Logging Requirements

Before diving into the configuration, it's important to clarify what we want to achieve:

Console Logging: Display only INFO logs to the console.

File Logging: Capture INFO, DEBUG, and ERROR logs in a designated file.

This setup allows for a clean console output while still keeping detailed logging for analysis in log files.

Step-by-Step Configuration

Setting this up in Logback involves editing the logback.xml configuration file. Here’s how to do it:

1. Basic Configuration

You should start with a basic logging level set in your application.properties file. This file will typically contain the following line:

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

2. Configuring Logback

Next, modify your logback.xml configuration file to create the appropriate appenders. Below is a sample configuration:

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

3. Fine-Tuning Log Levels for Different Outputs

To ensure that only INFO logs appear in the console, and INFO, DEBUG, and ERROR logs go to the file, you can use the spring profile settings shown below:

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

4. Explanation of the Configuration

CONSOLE Appender: This appender pushes logs to the console with a set format.

ROTATE_FILE_DAILY Appender: This appender ensures that logs are written into a file that rotates daily, helping in keeping the log file size manageable.

Log Levels: Adjusting the log level in the root tags and for specific loggers allows for control over what gets printed.

INFO level in the root tag means only INFO and above messages are logged (higher severities).

Adding specific loggers under different conditions allows you to capture detailed logs (DEBUG) while excluding them from console output.

Conclusion

By properly configuring Logback, you can efficiently manage logging in your application. This approach ensures that developers and support teams have access to just the right level of details needed for monitoring and debugging without cluttering the console with excessive log data. Following the steps outlined above, you will find it straightforward to enhance your application's logging framework. Happy logging!