IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Configure project paths Live reloading »
Elastic Docs ›Filebeat Reference [7.8] ›Configure Filebeat

Load external configuration files

edit
IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.

Load external configuration files

edit

Filebeat can load external configuration files for inputs and modules, allowing you to separate your configuration into multiple smaller configuration files. See the Input config and the Module config sections for details.

On systems with POSIX file permissions, all Beats configuration files are subject to ownership and file permission checks. For more information, see Config File Ownership and Permissions in the Beats Platform Reference.

Input config

edit

For input configurations, you specify the path option in the filebeat.config.inputs section of the filebeat.yml file. For example:

filebeat.config.inputs:
  enabled: true
  path: inputs.d/*.yml

Each file found by the path Glob must contain a list of one or more input definitions.

The first line of each external configuration file must be an input definition that starts with - type. Make sure you omit the line filebeat.config.inputs from this file.

For example:

- type: log
  paths:
    - /var/log/mysql.log
  scan_frequency: 10s

- type: log
  paths:
    - /var/log/apache.log
  scan_frequency: 5s

It is critical that two running inputs DO NOT have overlapping file paths defined. If more than one input harvests the same file at the same time, it can lead to unexpected behavior.

Module config

edit

For module configurations, you specify the path option in the filebeat.config.modules section of the filebeat.yml file. By default, Filebeat loads the module configurations enabled in the modules.d directory. For example:

filebeat.config.modules:
  enabled: true
  path: ${path.config}/modules.d/*.yml

The path setting must point to the modules.d directory if you want to use the modules command to enable and disable module configurations.

Each file found by the Glob must contain a list of one or more module definitions.

The first line of each external configuration file must be a module definition that starts with - module. Make sure you omit the line filebeat.config.modules from this file.

For example:

- module: apache
  access:
    enabled: true
    var.paths: [/var/log/apache2/access.log*]
  error:
    enabled: true
    var.paths: [/var/log/apache2/error.log*]
« Configure project paths Live reloading »