Log4J2 NoSQL query
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
Fields In NoSQL Appender
Hi, Is there a way to configure the fields in getting logged through Log4j2 NoSQL appender. For example, if we chose not to log loggerName or source, then is there a way to disable this. -- with regards Kusmanjali Jenamoni
Source field in NoSQLAppender
We have a wrapper for log4j 2 APIs. So instead of directly calling the function we call custom class to do the logging. The problem with this aproach is the 'source' field stored in database has details of the custom log class and not the class which is calling it i.e all my fileName , linenumber have details of the custom class. Is there a way to update the 'source' field? -- with regards Kusmanjali Jenamoni