IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.

› ›

Kafka module

edit

Kafka module

edit

The kafka module collects and parses the logs created by Kafka.

When you run the module, it performs a few tasks under the hood:

Sets the default paths to the log files (but don’t worry, you can override the defaults)
Makes sure each multiline log event gets sent as a single event
Uses ingest node to parse and process the log lines, shaping the data into a structure suitable for visualizing in Kibana
Deploys dashboards for visualizing the log data

Compatibility

edit

The kafka module was tested with logs from versions 0.9, 1.1.0 and 2.0.0.

Set up and run the module

edit

Before doing these steps, verify that Elasticsearch and Kibana are running and that Elasticsearch is ready to receive data from Filebeat.

If you’re running our hosted Elasticsearch Service on Elastic Cloud, or you’ve enabled security in Elasticsearch and Kibana, you need to specify additional connection information before setting up and running the module. See Quick start: modules for common log formats for the complete setup.

To set up and run the module:

Enable the module:

deb and rpm:

filebeat modules enable kafka

mac:

./filebeat modules enable kafka

brew:

filebeat modules enable kafka

linux:

./filebeat modules enable kafka

win:

PS > .\filebeat.exe modules enable kafka

This command enables the module config defined in the modules.d directory. See Specify which modules to run for other ways to enable modules.

To see a list of enabled and disabled modules, run:

deb and rpm:

filebeat modules list

mac:

./filebeat modules list

brew:

filebeat modules list

linux:

./filebeat modules list

win:

PS > .\filebeat.exe modules list

Set up the initial environment:

deb and rpm:
```
filebeat setup -e
```
mac:
```
./filebeat setup -e
```
linux:
```
./filebeat setup -e
```
brew:
```
filebeat setup -e
```
win:
```
PS > .\filebeat.exe setup -e
```
The setup command loads the recommended index template for writing to Elasticsearch and deploys the sample dashboards (if available) for visualizing the data in Kibana. This is a one-time setup step.

The -e flag is optional and sends output to standard error instead of syslog.

The ingest pipelines used to parse log lines are set up automatically the first time you run the module, assuming the Elasticsearch output is enabled. If you’re sending events to Logstash, or plan to use Beats central management, also see Load ingest pipelines manually.
Run Filebeat.

If your logs aren’t in the default location, see Configure the module, then run Filebeat after you’ve set the paths variable.

deb and rpm:
```
service filebeat start
```
mac:
```
./filebeat -e
```
brew:
```
filebeat -e
```
linux:
```
./filebeat -e
```
win:
```
PS > Start-Service filebeat
```
If the module is configured correctly, you’ll see INFO Harvester started messages for each file specified in the config.

Depending on how you’ve installed Filebeat, you might see errors related to file ownership or permissions when you try to run Filebeat modules. See Config File Ownership and Permissions in the Beats Platform Reference for more information.
Explore your data in Kibana:
1. Open your browser and navigate to the Dashboard overview in Kibana: http://localhost:5601/app/kibana#/dashboards. Replace localhost with the name of the Kibana host. If you’re using an Elastic Cloud instance, log in to your cloud account, then navigate to the Kibana endpoint in your deployment.
2. If necessary, log in with your Kibana username and password.
3. Enter the module name in the search box, then open a dashboard and explore the visualizations for your parsed logs.
  
  If you don’t see data in Kibana, try changing the date range to a larger range. By default, Kibana shows the last 15 minutes.

Example dashboard

edit

This module comes with a sample dashboard to see Kafka logs and stack traces.

Configure the module

edit

You can further refine the behavior of the kafka module by specifying variable settings in the modules.d/kafka.yml file, or overriding settings at the command line.

The following example shows how to set paths in the modules.d/kafka.yml file to override the default paths for logs:

- module: kafka
  log:
    enabled: true
    var.paths:
      - "/path/to/logs/controller.log*"
      - "/path/to/logs/server.log*"
      - "/path/to/logs/state-change.log*"
      - "/path/to/logs/kafka-*.log*"

To specify the same settings at the command line, you use:

-M "kafka.log.var.paths=[/path/to/logs/controller.log*, /path/to/logs/server.log*, /path/to/logs/state-change.log*, /path/to/logs/kafka-*.log*]"

Variable settings

edit

Each fileset has separate variable settings for configuring the behavior of the module. If you don’t specify variable settings, the kafka module uses the defaults.

For more information, see Specify variable settings. Also see Override input settings.

When you specify a setting at the command line, remember to prefix the setting with the module name, for example, kafka.log.var.paths instead of log.var.paths.

`log` fileset settings

edit

var.paths: An array of glob-based paths that specify where to look for the log files. All patterns supported by Go Glob are also supported here. For example, you can use wildcards to fetch all files from a predefined level of subdirectories: /path/to/log/*/*.log. This fetches all .log files from the subfolders of /path/to/log. It does not fetch log files from the /path/to/log folder itself. If this setting is left empty, Filebeat will choose log paths based on your operating system.

Timezone support

edit

This module parses logs that don’t contain timezone information. For these logs, Filebeat reads the local timezone and uses it when parsing to convert the timestamp to UTC. The timezone to be used for parsing is included in the event in the event.timezone field.

To disable this conversion, the event.timezone field can be removed with the drop_fields processor.

If logs are originated from systems or applications with a different timezone to the local one, the event.timezone field can be overwritten with the original timezone using the add_fields processor.

See Filter and enhance the exported data for information about specifying processors in your config.

Fields

edit

For a description of each field in the module, see the exported fields section.

« Iptables module Kibana module »

Kafka module

Kafka module

Compatibility

Set up and run the module

Example dashboard

Configure the module

Variable settings

log fileset settings

Timezone support

Fields

`log` fileset settings