Redis Logs

Redis log monitoring could be a painful process. To ease this, OpManager Nexus AppLogs has already segregated crucial log components and sorted them under different field names before they are presented to the user as PID, roles, date & time, log level, and message.  Learn more about log management with OpManager Nexus.

Getting started

1. Log in to your OpManager Nexus account.
2. Download and install the OpManager Nexus Server Monitoring agent (Windows | Linux). 
3. Go to Admin > AppLogs > Log Profile and Add Log Profile.

Logs file path

Each application writes logs in different folders and files. By default, Redis logs are sourced from the below-mentioned folder path for the respective Operating System. If you have logs in a different folder, you can mention it under the File Path to source them from that particular folder while creating a log profile.

:

/var/log/redis/redis*.log

:

C:\redis*\logs\redis*.log

Log pattern

$PID:number$:$Role$ $DateTime:date$ $LogLevel$ $Message$

This is the default pattern defined by OpManager Nexus for parsing Redis logs based on the sample log mentioned below.

Sample log

3489:M 06 Mar 09:13:40.537 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.

The above sample log can be separated into 5 fields, each of which will take its respective value from here and will then be uploaded to OpManager Nexus.

Related log types

• Syslogs
• Cron logs
• Other supported log types