On Tue, Oct 24, 2023, at 22:30, Robert Middleton wrote:
> Those classes are to receive log events from a database table. Log4j1
> and log4cxx can write log messages directly to a database; I'm not
> sure about log4j2.
Yes, there is a JDBC Appender that is discussed more often these days
>
On Tue, Oct 24, 2023, at 22:19, Matt Sicker wrote:
> If you use Log4j in Chainsaw, you could set up a JDBC appender or
> similar to forward things along. The Flume appender could be useful
> there, too, but that sort of moves the database configuration into your
> Flume config.
I see - but
Those classes are to receive log events from a database table. Log4j1
and log4cxx can write log messages directly to a database; I'm not
sure about log4j2.
I'm not sure exactly what it does/how it does it, but it's going to
effectively do something like "SELECT * FROM Logs" and then pass those
If you use Log4j in Chainsaw, you could set up a JDBC appender or similar to
forward things along. The Flume appender could be useful there, too, but that
sort of moves the database configuration into your Flume config.
> On Oct 24, 2023, at 3:14 PM, Christian Grobmeier wrote:
>
> Hi,
>
> in
Hi,
in this package:
org.apache.log4j.db
all classes are commented. I am tempted to just remove it in full, but I am not
sure what i was supposed to do.
Docs read:
"Provides means to append logging events into various databases."
Does that mean, Chainsaw would collect logs and then send it
