WARNING: Version 6.1 of Metricbeat has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
Load external configuration files
editLoad external configuration files
editMetricbeat can load external configuration files for modules, which allows you
to separate your configuration into multiple smaller configuration files. To use
this, you specify the path option under metricbeat.config.modules in the
main metricbeat.yml configuration file. By default, Metricbeat loads the
module configurations enabled in the modules.d
directory. For example:
metricbeat.config.modules:
path: ${path.config}/modules.d/*.yml
-
path -
A Glob that defines the files to check for changes.
This setting must point to the
modules.ddirectory if you want to use themodulescommand to enable and disable module configurations.
Each file found by the Glob must contain a list of one or more module definitions. For example:
- module: system metricsets: ["cpu"] enabled: false period: 1s - module: system metricsets: ["network"] enabled: true period: 10s
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.