KMS Log Overview

Log Description

Log path: /var/log/Bigdata/kms (run log), /var/log/Bigdata/audit/kms (audit log)

Log archive rule: The automatic KMS log compression function is enabled. By default, when the size of a log file exceeds 50 MB, the log file is automatically compressed. A maximum of 100 compressed files can be reserved. The number of compressed files can be configured on FusionInsight Manager.

**Table 1** KMS log file list
Log Type	Log File Name	Description
Run log	kms-service-check.log	Log of the service health check
	yarn-postinstall.log	Log generated when the installation is complete
	yarn-prestart.log	Log generated before startup
	yarn-start-stop.log	Startup log
	kms-<SSH_USER>-<DATA>-<PID>-gc.log	Garbage collection log of KMS
	hadoop-<SSH_USER>-kms-<hostname>.log	Run log
	hadoop.log	Log generated by HDFS commands
	env.log	Environment information generated during startup and stopping
	threadDump-<DATE>.log	Stack information log printed by the Java process
Audit log	kms-audit.log	KMS operation audit log

Log Levels

Table 2 describes the log levels supported by KMS. The priorities of log levels are FATAL, ERROR, WARN, INFO, and DEBUG in descending order. Logs whose levels are higher than or equal to the specified level are printed. The number of printed logs decreases as the specified log level increases.

**Table 2** Log levels
Level	Description
FATAL	Logs of this level record fatal error information about the current event processing that may result in a system crash.
ERROR	Logs of this level record error information about the current event processing, which indicates that system running is abnormal.
WARN	Logs of this level record abnormal information about the current event processing. These abnormalities will not result in system faults.
INFO	Logs of this level record normal running status information about the system and events.
DEBUG	Logs of this level record the system as well as system debugging information.

To modify log levels, perform the following operations:

Log in to FusionInsight Manager.
Choose Cluster > Name of the desired cluster > Services > KMS > Configurations.
Select 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 configurations take effect.

The configurations take effect immediately without the need to restart the service.

Log Formats

The following table lists the KMS log formats.

**Table 3** Log formats
Log Type	Component	Format	Example
Run log	KMS	<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>	2019-05-29 11:25:12,331 \| INFO \| main \| KMS metrics system started \| MetricsSystemImpl.java:191
Audit log	KMS	<yyyy-MM-dd HH:mm:ss,SSS>\|<Log level>\|<Message in the log>	2019-05-30 14:56:13,159 \| INFO \| OK[op=GENERATE_EEK, key=cj1, user=hdfs, accessCount=1, interval=10692ms]