Kafka Logs
OpManager Nexus AppLogs makes Kafka log management simple as the log content is sliced into various appropriate fields such as date & time, log level, thread name, source file name, line number, and message. With this you can quickly pinpoint the required information over several lines of log data. Learn more about log management with OpManager Nexus.
Getting started
- Log in to your OpManager Nexus account.
- Download and install the OpManager Nexus Server Monitoring agent (Windows | Linux).
- Go to Admin > AppLogs > Log Profile and Add Log Profile.
Logs file path
Each application writes logs in different folders and files. By default, Kafka 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.


Log pattern
$DateTime:date$ - $LogLevel$ [$ThreadName$:$SourceFileName$@$LineNumber:number$] - $Message$
This is the default pattern defined by OpManager Nexus for parsing Kafka logs based on the sample mentioned below.
Sample log
2017-03-14 18:24:15,495] INFO [Controller 0]: List of topics to be deleted: 143 (kafka.controller.KafkaController)
The above sample log can be separated into 6 fields, each of which will take its respective value from here and will then be uploaded to OpManager Nexus.
| Field name | Field value |
| Date Time | 2017-03-14 18:24:15,495 |
| Log Level | INFO |
| Thread Name | Controller 0 |
| Source File Name | List of topics to be deleted |
| Line Number | 143 |
| Message | kafka.controller.KafkaController |
Related log types
-
On this page
- Getting started
- Logs file path
- Log pattern
- Sample log
- Related log types