Configure Log4j for Bloomreach Cloud

Overview

This page describes how to configure Log4j for Bloomreach Experience Manager projects deployed on Bloomreach Cloud.

Supported Log4j Version

Bloomreach Cloud supports Log4j version 2.x. Application logs are accessible through Humio. Bloomreach provides account credentials for Humio access.

The platform captures the following log files:

audit.log
cms.log
site.log
catalina standard output

Log4j Configuration

If you created your Bloomreach Experience Manager project using a recent Bloomreach Experience Manager Maven archetype, Log4j is preconfigured.

Hint: The Log4j configuration file must be named log4j2.xml.

If your project was created with an older archetype version, upgraded from an older version, or was not created using the archetype, verify that your Log4j configuration matches the following pattern:

<!-- cms.log -->
<RollingFile name="cms" fileName="${sys:catalina.base}/logs/cms.log"
             filePattern="${sys:catalina.base}/logs/cms.log.%d{yyyy-MM-dd}">
  <LookupFilter key="jndi:logging/contextName" value="cms" onMatch="ACCEPT"/>
  <PatternLayout pattern="%d{dd.MM.yyyy HH:mm:ss} %-5p [%C.%M():%L] %m%n"/>
  <Policies>
    <TimeBasedTriggeringPolicy/>
  </Policies>
</RollingFile>

Warning: Do not configure Log4j to write log messages to standard output or standard error. Logs sent to these streams will not appear in Humio.