You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Jörn Franke (Jira)" <ji...@apache.org> on 2019/11/10 19:38:00 UTC

[jira] [Created] (SOLR-13919) RefGuide: Add example for AuditLogger to use log4j to log into separate files

Jörn Franke created SOLR-13919:
----------------------------------

             Summary: RefGuide: Add example for AuditLogger to use log4j to log into separate files
                 Key: SOLR-13919
                 URL: https://issues.apache.org/jira/browse/SOLR-13919
             Project: Solr
          Issue Type: Improvement
      Security Level: Public (Default Security Level. Issues are Public)
          Components: SolrCloud
    Affects Versions: 8.3
            Reporter: Jörn Franke


At the moment, the Solr reference guide provides an example on how to log audit events to the standard Solr log (see [https://lucene.apache.org/solr/guide/8_3/audit-logging.html).] Those events are logged in the standard Solr log.

This enhancement proposes to include a simple explanation in the reference guide on how to configure log4j to log audit events in a separate file (this is possible already now with log4j, this issue is just about adding an example).

Reasoning behind this is that it can reduce the load on a SIEM system significantly as it only needs to process the relevant audit logs.

To be discussed: Should there be a standard log4j configuration when installing Solr to log into a separate file (maybe even the same log directory by default) all audit event



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org