SLF4J Alternatives

SLF4J reviews and mentions

• dazl — a facade for configurable/pluggable Go logging
  2 projects | /r/golang | 21 Apr 2023

  A few years ago, my team moved from Java to Go. Working on Go projects, we encountered a wide variety of logging frameworks with different APIs, configuration, and formatting. We soon found ourselves longing for a logging abstraction layer like Java’s slf4j, which had proven invaluable for use in reusable libraries or configuring and debugging production systems. So, not long after moving to Go, we began working toward replacing what we had lost in slf4j.

• Fargate logging thru console awslogs or directly to Cloudwatch?
  2 projects | /r/aws | 7 Apr 2023

  I'm not familiar with Serilog as I code mostly in Java, use slf4j (logs to stdout) and our apps send logs to Cloudwatch using the task definition's awslogs configuration. I prefer it this way because I can customize the log configurations in my task definitions. Also the default stream name has this format prefix-name/container-name/ecs-task-id so I can easily identify the logs of the task I want to look at. I haven't experienced any downsides with this approach and our apps publish a shit ton of logs. Cloudwatch approach looks like you can customize the stream name?

• Logging in your API
  13 projects | dev.to | 22 Feb 2023

  Java -> Logback, Log4j2, JDK (Java Util Logging), Slf4j, e.t.c.

• Primeiros passos no desenvolvimento Java em 2023: um guia particular
  13 projects | dev.to | 19 Jan 2023

  slf4j para padronização dos logs;

• What are some of the biggest problems you personally face in Java?
  6 projects | /r/java | 27 Dec 2022
• must known frameworks/libs/tech, every senior java developer must know(?)
  6 projects | /r/java | 9 Dec 2022

  SLF4J

• Go standard library: structured, leveled logging
  11 projects | news.ycombinator.com | 11 Sep 2022

  > My God. Logging in protobuf?

  Yes, or any other data format and/or transport protocol.

  I'm surprised this is up for debate.

  > Logging is the lowest of all debugging utilities - its the first thing you ever do writing software - “hello world”. And, while I admire structural logging, the truth is printing strings remains (truly) the lowest common denominator across software developers.

  This sort of comment is terribly miopic. You can have a logging API, and then configure your logging to transport the events anywhere, any way. This is a terribly basic feature and requirement, and one that comes out of the box with some systems. Check how SLF4J[1] is pervasive in Java, and how any SLF4J implementation offers logging to stdout or a local file as a very specific and basic usecase.

  It turns out that nowadays most developers write software that runs on many computers that aren't stashed over or under their desks, and thus they need efficient and convenient ways to check what's happening either in a node or in all deployments.

  [1] https://www.slf4j.org/

• Log4j: The Pain Just Keeps Going and Going
  8 projects | news.ycombinator.com | 20 Jul 2022

  > Then apache decides to put new people on log4j, do a backward incompatible v2 design that nevertheless is worse than slf4j. Why?

  slf4j itself isn't a logging framework. It's a facade to logging frameworks.

  Simple Logging Facade for Java ( https://www.slf4j.org )

  It needs a logging framework behind it - log4j, log4j2, logback, commons, JUL.

  The question is "why do log4j2?"

  Logback went from the log4j1.x path ( https://logback.qos.ch )

  Log4j2 has a lot of features that weren't present when the project started ( https://en.wikipedia.org/wiki/Log4j#Apache_Log4j_2 ).

  There is a licensing difference between Logback (LGPL) and Log4jx (Apache Commons).

• Logger Dependency Injection
  2 projects | /r/golang | 13 Jul 2022

  I think the Go designers were seeing the mess in other platforms (e.g. Java's SLF4J) and just decided not to play that game from the start. I'm sure it was intentional that Go logging is not a pluggable API. I like that Go is opinionated, but there are some opinions I disagree with. This particular opinion was defeatist and guaranteed a mess rather than make even a small effort to make life easier for some if not all. END RANT.

• E2E-Testing in CI Environment With Testcontainers
  3 projects | dev.to | 21 Jun 2022

  Also, I'd like you to pay attention to the log consumer. You see, when the E2E scenario fails, it's not always obvious why. Sometimes to understand the source of the problem you have to dig into containers' logs. Thankfully the log consumer allows us to forward a container's logs to any SLF4J logger instance. In this project, containers' logs are forwarded to regular text files (you can find the Logback configuration in the repository). Though it's much better to transfer logs to external logging facility (e.g. Kibana).

• A note from our sponsor - Onboard AI
  getonboard.dev | 4 Oct 2023

  Onboard AI learns any GitHub repo in minutes and lets you chat with it to locate functionality, understand different parts, and generate new code. Use it for free at www.getonboard.dev. Learn more →