Date: Thu, 28 Mar 2024 19:39:01 +0000 (UTC) Message-ID: <1738707771.8342.1711654741750@support.blancco.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_8341_200921370.1711654741750" ------=_Part_8341_200921370.1711654741750 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Created date | Updated date | Affects version | Fix version |
---|---|---|---|
|
Blancco Management Console uses&nb= sp;Apa= che Tomcat, meaning a lot of Apache documentation can also be applied t= o Management Console. To generate logging files mentioned in this article, = see How to collect log files and system information= from the Management Console.
Blancco Management Console activit= y is logged in detail. Sometimes troubleshooting an issue might require ins= pecting the log files.
When generating the log files, two=
folders are created, config and lo=
gs. In addition, an sdt_report.txt is created from the Blancco Management Console Diagnostics Core which in=
cludes some system information and list of collected files from BMC.
Note! All access = log files (bmc_access_log.*) that are older (modification time) than 28 day= s, are automatically deleted. The deletion happens after the first HTTP req= uest after 00:00:00, when it also creates the new access log file for that day.
Blancco Management Console uses st= andard Apache Log4j2= a> as the logging framework. In addition, Apache Tomcat implements the= access logging.
Following directories are used for= storing log files:
Log4j configuration
The configuration file is located = at: [Installation path]\apache-tomcat\webapps\ROOT\WEB-INF\classes\log4j2.x= ml.
Blancco Management Console is requ=
ired to be restarted after changes of log configuration file.
The main log level can be set by XML=
element: <Root level=3D"info">
Available logging levels:
Log4j archives old log files into = ZIP files. The maximum size of open log file is defined by XML element <= SizeBasedTriggeringPolicy size=3D"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>-yyyy-mm-dd-n.log.zip
Apache Tomcat logging configuration
The access logging is implemented = by standard Apache Tomcat AccessLogValve in server.xml. By defaul= t the pattern is 'common' but also 'combined' can be used.
The access logs are written into d= aily files named bmc_access_log.<yyyy-mm-dd>.txt.