Skip to content

Exploring log4j alternatives, as log4j is inherently vulnerable by design

License

Notifications You must be signed in to change notification settings

sre-guy/log4j-alternatives

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

4 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Alternate Java loggers

Exploring log4j alternatives, as log4j is inherehtly vulnerable by design.

In this project, we explore 3 alternate logging libraries:

Capabilites and features for all these loggers are demonstrated via a simple "Hello-World" style Java application.

Run

Run the project with Gradle by running:

$ ./gradlew run

> Task :app:run
08:47:52.166 INFO  log4j.alternatives.Logback - This is an INFO level log message from Logback!
08:47:52.168 ERROR log4j.alternatives.Logback - This is an ERROR level log message from Logback!
08:47:52.248 log4j.alternatives.Tinylog.exec() INFO: This is an info log from tinylog, with number 9
08:47:52.249 log4j.alternatives.Tinylog.exec() ERROR: This is an error from tinylog
19/12/2021 08:47:52.252 Some message from minlog.
19/12/2021 08:47:52.255 Reading file reading file: /tmp/blah, msg from minlog

Quick Observations

  • Logback is by far the most extensible and can be used for more complex logging needs. Note that it does rely on slf4j, however.
  • Tinylog is extensible as well, but not to the same extent as Logback. It definitely removes a ton of logging overhead and follows a fairly minimalistic design.
  • Minlog is as simple as it gets, with sufficient logging capabilities for simple applications.

About

Exploring log4j alternatives, as log4j is inherently vulnerable by design

Topics

Resources

License

Stars

Watchers

Forks