If Kafka 4.0 is Java 11+, why would you use SLF4J instead of the Java
9+ logging facade System.Logger?
Hi Mickael,
I agree it's good to make it clear about what we're going to adopt for the
logging library.
For keeping reload4j or adopting log4j2, I don't have any preference TBH.
But if Viktor is willing to drive log4j2 tasks, then we don't have any
reason not to adopt log4j2. (Thanks Viktor!)
Tha
Hi,
I think the only thing that would need to be done in 3.8 is the
deprecation of the log4j appender (KIP-719). This was a pre-req for
migrating to log4j2 due to conflicts when having both log4j and log4j2
in the classpath. I don't know if that's still the case with reload4j
but I think we should
Hi Mickael,
Thanks for bringing this up.
If we move to log4j2 in 4.0, is there any work that needs to be done in 3.8?
That's probably what we should focus on.
P.S. My assumption is that if the log4j2 work misses the train, we'll stick
with reload4j in 4.0. Hopefully this won't happen.
best,
C
Hi Viktor,
A logging library that requires Java 17 is a deal breaker since we need to
log from modules that will only require Java 11 in Apache Kafka 4.0.
Ismael
On Wed, Jan 10, 2024 at 6:43 PM Viktor Somogyi-Vass
wrote:
> Hi Mickael,
>
> Reacting to your points:
> 1. I think it's somewhat unf
Hi Mickael,
Reacting to your points:
1. I think it's somewhat unfortunate that we provide an appender tied to a
chosen logger implementation. I think that this shouldn't be part of the
project in its current form. However, there is the sl4fj2 Fluent API which
may solve our problem and turn KafkaLo
Hi,
A couple of PMC members from Apache Logging replied and they said they
plan to keep supporting log4j2 for several years.
https://lists.apache.org/thread/6n6bkgwj8tglgdgzz8wxhkx1p1xpwodl
Thanks,
Mickael
On Wed, Jan 10, 2024 at 3:57 PM Mickael Maison wrote:
>
> I asked for details about the f
I asked for details about the future of log4j2 on the logging user list:
https://lists.apache.org/thread/6n6bkgwj8tglgdgzz8wxhkx1p1xpwodl
Let's see what they say.
Thanks,
Mickael
On Wed, Jan 10, 2024 at 3:23 PM Ismael Juma wrote:
>
> Hi Mickael,
>
> Thanks for starting the discussion and for su
Hi Mickael,
Thanks for starting the discussion and for summarizing the state of play. I
agree with you that it would be important to understand how long log4j2
will be supported for. An alternative would be sl4fj 2.x and logback.
Ismael
On Wed, Jan 10, 2024 at 2:17 PM Mickael Maison
wrote:
> H
Hi,
Starting a new thread to discuss the current logging situation in
Kafka. I'll restate everything we know but see the [DISCUSS] Road to
Kafka 4.0 if you are interested in what has already been said. [0]
Currently Kafka uses SLF4J and reload4j as the logging backend. We had
to adopt reload4j in
[
https://issues.apache.org/jira/browse/KAFKA-8839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinoth Chandar resolved KAFKA-8839.
---
Resolution: Fixed
Closing since the PR has been merged
> Improve logging in Kafka Stre
Vinoth Chandar created KAFKA-8839:
-
Summary: Improve logging in Kafka Streams around debugging task
lifecycle
Key: KAFKA-8839
URL: https://issues.apache.org/jira/browse/KAFKA-8839
Project: Kafka
12 matches
Mail list logo
