Elasticsearch module

This is the elasticsearch module.

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 an Elasticsearch ingest pipeline to parse and process the log lines, shaping the data into a structure suitable for visualizing in Kibana

The Elasticsearch module is compatible with Elasticsearch 6.2 and newer.

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

You must enable at least one fileset in the module. Filesets are disabled by default.

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

For advanced use cases, you can also override input settings. See Override input settings.

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.

Example config:

server:
  enabled: true
  var.paths:
    - /var/log/elasticsearch/*.log
    - /var/log/elasticsearch/*_server.json

1. Plain text logs
2. JSON logs

Note

If you’re running against Elasticsearch >= 7.0.0, configure the var.paths setting to point to JSON logs. Otherwise, configure it to point to plain text logs.

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.

Example config:

gc:
  var.paths:
    - /var/log/elasticsearch/gc.log.[0-9]*
    - /var/log/elasticsearch/gc.log

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.

Example config:

audit:
  var.paths:
    - /var/log/elasticsearch/*_access.log
    - /var/log/elasticsearch/*_audit.json

1. Plain text logs
2. JSON logs

Note

If you’re running against Elasticsearch >= 7.0.0, configure the var.paths setting to point to JSON logs. Otherwise, configure it to point to plain text logs.

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.

Example config:

slowlog:
  var.paths:
    - /var/log/elasticsearch/*_index_search_slowlog.log
    - /var/log/elasticsearch/*_index_indexing_slowlog.log
    - /var/log/elasticsearch/*_index_search_slowlog.json
    - /var/log/elasticsearch/*_index_indexing_slowlog.json

1. Plain text logs
2. Plain text logs
3. JSON logs
4. JSON logs

Note

If you’re running against Elasticsearch >= 7.0.0, configure the var.paths setting to point to JSON logs. Otherwise, configure it to point to plain text logs.

var.paths

An array of glob-based paths that specify where to look for the query log files. All patterns supported by Go Glob are also supported here. This fileset ingests Elasticsearch query log JSON only (one JSON object per line). 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.

Example config:

querylog:
  enabled: true
  var.paths:
    - /var/log/elasticsearch/*_querylog.json

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.

Example config:

deprecation:
  var.paths:
    - /var/log/elasticsearch/*_deprecation.log
    - /var/log/elasticsearch/*_deprecation.json

1. Plain text logs
2. JSON logs

Note

If you’re running against Elasticsearch >= 7.0.0, configure the var.paths setting to point to JSON logs. Otherwise, configure it to point to plain text logs.

This module parses logs that don’t contain time zone information. For these logs, Filebeat reads the local time zone and uses it when parsing to convert the timestamp to UTC. The time zone 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 time zone to the local one, the event.timezone field can be overwritten with the original time zone using the add_fields processor.

See Processors for information about specifying processors in your config.

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