1. Most of the logging frame works use a log forwarder + queue
mechanism(Logstash, Fluectd) to store logs into database. What is the
advantage of using this over using Log4j NoSQL appenders to write directly
to the database.

2. Any material/link to get more insight into how log4j2 handles the
database connection and failover. And how we can scale this architecture to
store logs from multiple servers into a single database.

Our idea is to build a central logging system just by using Log4 and doing
away with forwarders and queues.

-- 
with regards
Kusmanjali Jenamoni

Reply via email to