This tool enhances the Simple Logging Facade for Java library with the capability of
formatting parameters using ANSI escape codes, which are defined as styles using
the Jansi library. In addition, overall styles can be defined for each logging level (ERROR
,
WARN
,INFO
,DEBUG
, TRACE
).
If your console or log storing system does not work nicely with ANSI escape codes, you can simply disable this feature and your messages will be logged without them, while you are not required to change your code.
<dependency>
<groupId>io.github.luiinge</groupId>
<artifactId>slf4j-ansi</artifactId>
<version>1.0.0</version>
</dependency>
Just create an AnsiLogger
wrapper around your Slf4J logger:
Logger logger = AnsiLogger.of(LoggerFactory.getLogger(YourClass.class);
After that, when you want to embed a parameter in a message, you can indicate the style inside the brackets:
logger.info("The service endpoint is {uri}", "http://myserver:8080/service");
logger.warn("A timeout of {} seconds has ocurred requesting the resource {resource}", 4, "data.json");
If you want to add/replace styles, you should configure AnsiLogger
in some initializing method of your application, so that the styles are applied from the very beginning:
public static void someInitializerMethod() {
Properties customStyles = new Properties();
customStyles.put("resource","magenta,underline,bold");
...
AnsiLogger.setStyles(customStyles);
}
Apart from the style of each argument of the message, you can define an overall style applied to the whole message, using the syntax {!style}
at the beggining:
logger.info("{!important} This is an important message");
Each log level defined in the SLF4J API use an overall style identified respectively by error
, warn
, info
, debug
, and trace
. You can overwrite these styles, and even use them with another log level:
logger.debug("{!warn} This is a debug message formatted using the style of warn messages");
It is possible to manually enable / disable the formatting:
AnsiLogger.setEnabled(false);
When disabled, no Ansi codes are generated whatsoever. It is useful if you want to activate/deactivate this feature according to some argument or configuration provided externally.
The built-in styles provided by default are the following:
Style | Definition |
---|---|
error |
red,bold |
warn |
yellow,bold |
trace |
faint |
uri |
blue,underline |
id |
cyan,bold |
important |
magenta,bold |
highlight |
white,bold |
The recognized styles are defined by Jansi codes (can be combined with commas), which are:
Code | Representation |
---|---|
black |
black text color |
red |
red text color |
green |
green text color |
yellow |
yellow text color |
blue |
blue text color |
magenta |
magenta text color |
cyan |
cyan text color |
white |
white text color |
bold |
bold text intensity |
faint |
faint text intensity |
underline |
underline text |
blink_slow |
text blinking at low rate |
blink_fast |
text blinking at high rate |
bg_black |
black background color |
bg_red |
red background color |
bg_green |
green background color |
bg_yellow |
yellow background color |
bg_blue |
blue text background |
bg_magenta |
magenta background color |
bg_cyan |
cyan background color |
bg_white |
white background color |
Be aware that the use of this library will add extra computational cost to your underlying logging system. For this reason, it is not recommended in scenarios where performance may be an issue, for example extensive logging during long operations. Also, logging to targets other than console will produce the same ANSI codes. Thus, it might difficult the readability of the messages if the visualizer tool used does not support ANSI.
- Luis Iñesta Gelabert | luiinge@gmail.com
If you want to contribute to this project, visit the Github project. You can open a new issue / feature request, or make a pull request to consider. You will be added as a contributor in this very page.
If you have found any defect in this software, please report it in Github project Issues. There is no guarantee that it would be fixed in the following version but it would be addressed as soon as possible.
MIT License
Copyright (c) 2020 Luis Iñesta Gelabert
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.