Introduction to Containers Logs

Log Description

Log path:

Run log: /var/log/Bigdata/containers/container/Container_Instance ID/
Audit log: /var/log/Bigdata/audit/containers/container/Container_Instance ID/
Containers-tomcat log: /var/log/Bigdata/tomcat/container/
Container instance installation and uninstallation log: /var/log/Bigdata/containers/

Log archive rule: The automatic compression and archive function is enabled for Containers logs. By default, when the total size of all log files exceeds 5 MB (configurable), the log files are automatically compressed into a package named in the format of Original log file name-yyyy-mm-dd_hh-mm-ss.No..log.zip. The number of compressed files to be retained and the compression threshold are configurable.

**Table 1** WebContainer log list
Log Type	Log File	Description
Run log	blus	Directory for storing BLU run log files
	cleanupDetail.log	BLU clearance log file
	container-catalina-omm-hostname.log	Tomcat run logs
	container-catalina-omm-hostname.out	Output of the Tomcat console, which is equivalent to the Catalina.out log (this log is not compressed in rolling mode).
	container-common-omm-hostname.log	Containers health monitoring log files
	container-gc-omm-hostname.log.ID.current	GC log of the Tomcat process
	container-manager-omm-hostname.log	Management log of the Tomcat process
	container-servlet-omm-hostname.log	Containers run logs
	postinstallDetail.log	Containers installation log
	startDetail.log	Containers startup log
	stopDetail.log	Containers stop log
	container-stack-omm-hostname.time.log	Stack information before Containers is stopped
Containers instance installation and uninstallation log	containers_install.log	Containers instance installation and uninstallation log
Containers-tomcat log	sgpaudit.log	Audit log of Sqp management operations in Containers
	web_container_audit.log	Audit log of Containers operations
	web_container.log	Containers monitoring run log
	web_sgp_control.log	Log of the Sgp module in Containers
	web_sgp.log	Core run log of the Sgp module in Containers
	backup.log	Containers backup and restoration log
	/script/container_script.log	Log about tool.sh during BLU deployment in Containers
Audit log	container-audit-omm-hostname.log	Containers audit log

Log Levels

Table 2 describes the log levels provided by Containers.

The log levels are ERROR, WARN, INFO, and DEBUG in descending order of priority. Only logs whose levels are higher than or equal to the specified level are recorded. The higher the log level specified, the fewer the logs are recorded.

**Table 2** Log levels
Level	Description
ERROR	Logs of this level record error information about system running
WARN	Logs of this level record exception information about the current event processing
INFO	Logs of this level record normal running status information about the system and events
DEBUG	Logs of this level record the system information and system debugging information

To modify log levels, perform the following operations:

Log in to FusionInsight Manager.
Choose Cluster > Services > Containers. Click Configurations then All Configurations.
On the menu bar on the left, select the log menu of the target role.
Select a desired log level.
Click Save. In the displayed dialog box, click OK to make the configuration take effect.

Log Formats

The following table lists the Containers log formats:

**Table 3** Log formats
Log type	Format	Example Value
Run log	<yyyy-MM-dd HH:mm:ss,SSS>\|<Log level>\|<Name of the thread that generates the log>\|<Message in the log>\|<Location where the log event occurs>	15/03/16 09:24:48 DEBUG [container-deploy-checker] [task-checker] task: [taskName=com.xxx.dap.container.servlets.operation.deploy.task.DeployTask@2e0bc2ef][submitTime=1426469087953][overTime=60000][taskPriority=LOWEST_PRIORITY][taskSeqno=10238] done com.xxx.dap.container.servlets.operation.deploy.task.TaskChecker.run(TaskChecker.java:42)