LOGBack VS Angle-grinder

• Performance
  LOGBack is designed to be performant with efficient computation and low memory footprint, making it suitable for high-load applications.
• Configuration
  It offers a flexible and powerful configuration via XML or Groovy, allowing detailed customization for logging behavior.
• Integration
  Seamless integration with SLF4J provides a standard API for various logging frameworks, simplifying the logging implementation.
• Rolling Policies
  Includes advanced rolling policies for log files, including time-based and size-based rotation, ensuring log management is efficient and organized.
• Community Support
  Active community support and comprehensive documentation make it easier for developers to troubleshoot and enhance their implementation.

Possible disadvantages

• Complexity
  The configuration complexity may be overwhelming for beginners who need only basic logging functionalities.
• Dependency
  Adding LOGBack to a project increases the number of dependencies, which can affect project size and complexity management.
• Learning Curve
  For developers unfamiliar with SLF4J or complex logging requirements, there might be a steep learning curve.
• Legacy Systems
  Integration with older systems that rely on legacy logging frameworks might require additional adjustments or code refactoring.

No features have been listed yet.

Tracking LOGBack since Mar 2021.

• Ngtop – Request analytics from the Nginx access logs

  Found it much easier to just used structured logs and slice them with [angle grinder](https://github.com/rcoh/angle-grinder). - Source: Hacker News / about 2 years ago

• Show HN: How did I live without Pipe Watch?

  Seems like similar to lnav[1] or angle-grinder[2]. [1] https://lnav.org/ [2] https://github.com/rcoh/angle-grinder. - Source: Hacker News / over 4 years ago