Logback alternatives and similar libraries
Based on the "Logging" category.
Alternatively, view Logback alternatives based on common mentions on social networks and blogs.
9.7 10.0 L3 Logback VS kibanaAnalyzes and visualizes log files. Some features require payment.
8.7 9.9 L4 Logback VS graylogOpen-source aggregator suited for extended role and permission management.
7.0 8.9 L3 Logback VS Apache Log4j 2Complete rewrite with a powerful plugin and configuration architecture.
5.6 8.7 L5 Logback VS LogbookExtensible, open-source library for HTTP request and response logging.
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest. Visit our partner's website for more details.
Do you think we are missing an alternative of Logback or a related project?
Thank you for your interest in logback, the reliable, generic, fast and flexible logging library for Java.
The Logback documentation can be found on the project web-site as well as under the docs/ folder of the logback distribution.
Version 1.3.x requires Java 9 to compile and build.
More details on building logback is documented at:
In case of problems
In case of problems please do not hesitate to post an e-mail message on the [email protected] mailing list. However, please do not directly e-mail logback developers. The answer to your question might be useful to other users. Moreover, there are many knowledgeable users on the logback-user mailing lists who can quickly answer your questions.
If you are interested in improving logback, great! The logback community looks forward to your contribution. Please follow this process:
- Please file a bug report. Pull requests with an associated JIRA issue will get more attention.
Optional: Start a discussion on the logback-dev mailing list about your proposed change.
Fork qos-ch/logback. Ideally, create a new branch from your fork for your contribution to make it easier to merge your changes back.
Make your changes on the branch you hopefuly created in Step 2. Be sure that your code passes existing unit tests.
Please add unit tests for your work if appropriate. It usually is.
Push your changes to your fork/branch in github. Don't push it to your master! If you do it will make it harder to submit new changes later.
Submit a pull request to logback from from your commit page on github.