WARNING: Version 6.1 of Filebeat 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.
Live reloading
editLive reloading
editYou can configure Filebeat to dynamically reload configuration files when there are changes. This feature is available for prospector and module configuration files only.
To configure this feature, you specify a path (Glob) to watch for configuration changes. When the files found by the Glob change, new prospectors and/or modules are started and stopped according to changes in the configuration files.
This feature is especially useful in container environments where one container is used to tail logs for services running in other containers on the same host.
To enable dynamic config reloading, you specify the path and reload options
under filebeat.config.prospectors or filebeat.config.modules sections. For
example:
filebeat.config.prospectors: enabled: true path: configs/*.yml reload.enabled: true reload.period: 10s
-
path - A Glob that defines the files to check for changes.
-
reload.enabled -
When set to
true, enables dynamic config reload. -
reload.period -
Specifies how often the files are checked for changes. Do not
set the
periodto less than 1s because the modification time of files is often stored in seconds. Setting theperiodto less than 1s will result in unnecessary overhead.
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.