Redis Log Overview

Log Description

Log path

Default path of Redis logs: /var/log/Bigdata/redis/role name
Default path of Redis-Data-Sync logs: /var/log/Bigdata/redis/tomcat
Path of HTTPS request access logs: /var/log/Bigdata/redis/catalina

Log archive rule: The automatic compression and archive function is enabled for Redis logs. By default, when the size of a log file exceeds 10 MB, the log file is automatically compressed. The naming rule of the compressed log file is as follows: <Original log name>.<yyyy-mm-dd_hh-mm-ss>.log.tar.gz. The compressed log files are stored in the same directory as the original log files. A maximum of 20 latest compressed log files can be stored.

**Table 1** Redis log list
Type	Name	Description
Redis process run log	redis.log	Run log file of the main Redis process.
Redis process run log	redis_bg.log	Redis log file to start background threads. This log is recorded when bgsave is executed.
Script log	prestartDetail.log	Log file generated before the Redis Server is started.
	redis_cleanup.log	Log file that records the uninstallation or clearance of the Redis service.
	redis_install.log	Redis installation log file.
	redis_start.log	Logs that record the latest startup of the Redis process.
	redis_stop.log	Log file that records the latest shutdown of the Redis process.
Redis cluster management log	web_redis.log	redis-ws run log, which is stored in /var/log/Bigdata/redis/tomcat/redis by default
Redis cluster management log	redisweb_audit.log	Audit logs of Redis cluster creation, scale-out, scale-in, and deletion
Redis-Data-Sync logs	rds_start.log	Logs that record the latest startup of the Redis-Data-Sync instance.
	rds_stop.log	Logs that record the latest shutdown of the Redis-Data-Sync instance.
	redis-data-sync.log	Run logs of the Redis-Data-Sync instance.
	redis_install.log	Logs that record Redis-Data-Sync instance installation.
	redis_cleanup.log	Logs that record the uninstallation or clearance of the Redis-Data-Sync instance.
	redis-data-sync-username--pidxxxx-gc.log.x.current	GC logs.
	catalina.out	Tomcat Catalina standard output logs
	catalina.Y-M-D.log	Catalina logs.
	manager.Y-M-D.log	Tomcat management logs.
	host-manager.Y-M-D.log	Logs of virtual Tomcat hosts.
	localhost_access_log..Y-M-D.txt	HTTPS request access logs.
	rds_instance_check.log	Health check log of the Redis-Data-Sync instance
	redisDataSyncThreadDump*.log	Redis-Data-Sync instance stack information

Log levels

Table 2 describes the log levels provided by Redis.

Levels of Redis process run logs are warning, notice, verbose, and debug from the highest to the lowest priority. Run logs of equal or higher levels are recorded. The higher the specified log level, the fewer the logs recorded.

The script log levels are ERROR, WARN, INFO, and DEBUG.

Redis cluster management logs: ERROR, WARN, INFO, and DEBUG.

Redis-Data-Sync logs: ERROR, WARN, INFO, and DEBUG.

**Table 2** Log levels
Log Type	Level	Description
Run logs	warning	Logs of this level record only important information.
	notice	Logs of this level record suitable details and are applicable to the production environment.
	verbose	Logs of this level record normal running status information about the system and events.
	debug	Logs of this level record system running and debugging information.
Script logs	ERROR	Logs of this level record error information about system running.
	WARN	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.
Redis cluster management log	ERROR	Logs of this level record error information about system running.
	WARN	Exception information about the current event processing
	INFO	Normal running status information about the system and events.
	DEBUG	Logs of this level record the system information and system debugging information.
Redis-Data-Sync logs	ERROR	Logs of this level record error information about system running.
	WARN	Exception information about the current event processing
	INFO	Normal running status information about the system and events.
	DEBUG	Logs of this level record the system information and system debugging information.

To change the run log level of the Redis process, perform the following operations:

Log in to FusionInsight Manager.
Choose Cluster > Name of the target cluster and click the Configurations tab and then All Configurations.
In the navigation pane on the left, choose the target role > Customization and change the name of redis.customized.configs to loglevel and the value to the required log level.
Click Save. In the displayed dialog box, click OK.
Click Dashboard, choose More, and select Restart Service in the upper-right corner to restart the Redis service.

Log Format

The Redis log format is as follows:

**Table 3** Log Format
Log Type	Format	Example
Run logs	[yyyy-MM-dd HH:mm:ss] [Process PID] [Role of the Redis process] [Log level] <Log message>[Location where the log event occurs]	[2019-03-13 17:04:28][014769][M][notice] The server is now ready to accept connections on port 22400[redis.c:3722]
Script logs	[yyyy-MM-dd HH:mm:ss] <Log level <Log details > [Location where the log event occurs] (Process ID)	[2019-03-17 09:41:16] INFO Start redis instance success. [175(redis-start.sh)](20469)
Redis cluster management log	yyyy-MM-dd HH:mm:ss \| Log level \| Current thread \| Log details \| Log generation location	2020-07-17 15:53:26,416 \| INFO \| localhost-startStop-1 \| Begin to check redis status. \| com.xxx.redis.om.controller.RedisController.<clinit>(RedisController.java:78)
Redis-Data-Sync logs	yyyy-MM-dd HH:mm:ss \| Log level \| Current thread \| Log generation location \| Log details	2021-09-22 16:58:34.736\|INFO \|localhost-startStop-1\|ConfigurationManager.java:73\|ConfigurationManager initConf start

Redis process roles include X, C, M, and S. X indicates Sentinel. C indicates a subprocess written by AOF. M indicates the master role in the Redis cluster. S indicates a slave role in the Redis cluster.