Configure Log4j for Bloomreach Cloud - BloomReach Experience - Open Source CMS

Configure Log4j for Bloomreach Cloud

This documentation applies to Bloomreach Cloud 2 only

Introduction

Goal

Configure Log4j in your Bloomreach Experience Manager project for deployment in Bloomreach Cloud.

Background

Bloomreach Cloud supports Log4j version 1.x for Bloomreach Experience Manager 11 and Log4j version 2.x for Bloomreach Experience Manager 12 and later. These logs are exposed at Humio. Account details are provided by Bloomreach.

The Bloomreach Cloud platform captures the following output:

  • audit.log * 
  • cms.log  
  • site.log
  • catalina std out

* Note: In Log4j config  please use hippo-audit.log filename.  BRC Team is working on a fix to support also audit.log filename.

Log4j Configuration

Bloomreach Experience Manager projects created using a recent Bloomreach Experience Manager Maven archetype already have Log4j configured out-of-the-box.

If your project was created using an older version of the archetype and subsequently upgraded, or if your project was not created using the archetype at all, make sure your Log4j configuration looks similar to:

    <!-- 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>
Did you find this page helpful?
How could this documentation serve you better?
On this page
    Did you find this page helpful?
    How could this documentation serve you better?