Type to search.

Reload the configuration dynamically

Serverless Beta

Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud.

Availability

  • Beta

    This functionality is in beta and is not ready for production usage. For beta features, the design and code is less mature than official GA features and is being provided as-is with no warranties. Beta features are not subject to the support SLA of official GA features. Specific Support terms apply.

Serverless interfaces and procedures might differ from classic Elastic Stack deployments.

Stack Beta

The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats.

Availability

  • Beta

    This functionality is in beta and is not ready for production usage. For beta features, the design and code is less mature than official GA features and is being provided as-is with no warranties. Beta features are not subject to the support SLA of official GA features. Specific Support terms apply.

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.

Warning

This functionality is in beta and is subject to change. The design and code is less mature than official GA features and is being provided as-is with no warranties. Beta features are not subject to the support SLA of official GA features.

You can configure Auditbeat to dynamically reload configuration files when there are changes. To do this, you specify a path (glob) to watch for module configuration changes. When the files found by the glob change, new modules are started/stopped according to changes in the configuration files.

To enable dynamic config reloading, you specify the path and reload options in the main auditbeat.yml config file. For example:

Shell 
auditbeat.config.modules:
  path: ${path.config}/conf.d/*.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 period to less than 1s because the modification time of files is often stored in seconds. Setting the period to less than 1s will result in unnecessary overhead.

Each file found by the glob must contain a list of one or more module definitions. For example:

YAML 
- module: file_integrity
  paths:
  - /www/wordpress
  - /www/wordpress/wp-admin
  - /www/wordpress/wp-content
  - /www/wordpress/wp-includes
Note

On systems with POSIX file permissions, all Beats configuration files are subject to ownership and file permission checks. If you encounter config loading errors related to file ownership, see Config file ownership and permissions.