Versions Compared

Old Version 5

changes.mady.by.user Kyle Miller

Saved on

compared with

New Version Current

changes.mady.by.user Kyle Miller

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
maxLevel2

The logging.cfg file is a standard log4j configuration file. This section describes how to configure system and audit logging for the Gateway service. Additional information about log4j is available from the Apache Software Foundation's web site: logging.apache.org

Info

Upgrading from 5.x

The configuration file for logging changed from logging.cfg (log4j) to logging.yaml (log4j2) to support Elasticsearch 5.6. Add customizations to the YAML file. See Gateway Configuration. (v6.0)

...

The audit logging is configured within the logging.cfg file along with the system logging configuration. The audit logging uses the audit logger name in order to separate its the messages from the system messages. The name audit for the logger cannot be changed. Audit messages are logged at INFO level and each message event type can be filtered separately. Setting the log4j filter threshold to WARN, ERROR, or FATAL disables output of that message event type.

...

For direct control of the message event types, change the filtering threshold to INFO to enable and FATAL to disable the type. This example shows all message event types set to INFO in order to enable them.

Code Block
log4j.logger.audit.scsp = INFO, audit 
log4j.logger.audit.auth = INFO, audit 
log4j.logger.audit.domain = INFO, audit 
log4j.logger.audit.bucket = INFO, audit 
log4j.logger.audit.admin = INFO, audit

...