Cassandra System Logs

Log monitoring for Cassandra system logs is made simple and intuitive by OpManager Nexus AppLogs. We segregate essential information in an easily accessible format by splitting them into fields like log Level, thread name, date & time, source file name, line number, and message. OpManager Nexus AppLogs is an agent-based monitoring on the cloud that provides a secure and efficient monitoring solution for Cassandra system logs. 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.

Log file path

Each application writes logs in different folders and files. By default, Cassandra system logs are sourced from the below-mentioned folder path for the respective Operating System (OS). 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/cassandra/*

:

/home/sas/cassandra/data_directories/log/*

Log pattern

$LogLevel$ [$ThreadName$] $DateTime:date$ $SourceFileName$ (line $LineNumber:number$) $Message$

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

Sample log

INFO [main] 2016-11-04 02:14:23,494 DatabaseDescriptor.java (line 143) Data files directories: [/home/local/ZOHOCORP/franklin-0532/Softwares/Cassandra/data].

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

Related log types

• Log4j logs
• Kafka logs
• Other supported log types