Blancco Management Console uses standard Apache Log4j 2 as the logging framework. In addition, Apache Tomcat implements the access logging.

Following directories are used for storing log files:

  • Log4j: [Installation path]\logs\
  • Apache Tomcat: [Installation path]\apache-tomcat\logs\

Log4j configuration

The configuration file is located at: [Installation path]\apache-tomcat\webapps\ROOT\WEB-INF\classes\log4j2.xml.

Blancco Management Console is required to be restarted after changes of log configuration file.

The main log level can be set by XML element: <Root level="info">

Available logging levels:

  • trace - log all HTTP communication messages with erasure clients and Asset Management System (AMS)
    • NOTE! trace level logging is only available on BMC version 4.8.0 or newer.
  • debug - logs verbose debug information, not recommended in production
  • info - the default logging level of Blancco Management Console
  • audit - info level logging and audit logging to the separate file (audit.log)
  • warn - logs warnings and errors
  • error - logs only errors
  • off - logging is completely disabled

Log4j archives old log files into ZIP files. The maximum size of open log file is defined by XML element <SizeBasedTriggeringPolicy size="100MB"/>, separately for main.log and audit.log.

Archived log files are stored into date formatted path: [Installation path]/logs/archive-logs/<yyyy-mm>/<app|audit>

Apache Tomcat logging configuration

The access logging is implemented by standard Apache Tomcat AccessLogValve in server.xml. By default the pattern is 'common' but also 'combined' can be used.

The access logs are written into daily files named bmc_access_log.<yyyy-mm-dd>.txt.