Load external configuration files
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Generally available
Stack
Generally available
Metricbeat 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.