Blancco Management Console activity is logged in detail. Sometimes troubleshooting an issue might require inspecting the log files.
When generating the log files, two folders are created, config and logs. In addition, an sdt_report.txt is created from the Blancco Management Console Diagnostics Core which includes some system information and list of collected files from BMC.
build.properties - BMC information used when building the service
configuration.properties - All active configuration settings
log4j2.xml - Logging settings for BMC log files
main.properties - General, database, BI and report transfer settings
server.xml - Tomcat's main configuration file, includes the server port and HTTP Connector settings
wrapper.conf - Wrapper properties
audit.log - Logs all user activity
bmc_access_log - HTTP requests handled by the web server
host-manager.log - Logs of any related web applications (not used in BMC)
install.log - Logs from the initial install of BMC
localhost.log - Logs of the host
main.log - General activity of the service
manager.log - Logs of any related web applications (not used in BMC)
trace.log - Logs HTTP communication with erasure clients and Asset Management System (AMS), needs to be enabled by editing the logging level of log4j2.xml to trace
wrapper.log - Wrapper logs
Note! All access log files (bmc_access_log.*) that are older (modification time) than 28 days, are automatically deleted. The deletion happens after the first HTTP request after 00:00:00, when it also creates the new access log file for that day.
Configuring BMC logging levels
Blancco Management Console uses standard Apache Log4j2 as the logging framework. In addition, Apache Tomcat implements the access logging.
Following directories are used for storing log files: