Beats breaking changes

This list summarizes the most important breaking changes in Beats. For the complete list, go to Beats breaking changes.

To prevent custom ILM policies from breaking during upgrades, the default ILM policy name no longer includes the Beats version.

If you want to include the version, use the setup.ilm.policy_name configuration setting. For example:

setup.ilm.policy_name: "%{[agent.name]}-%{[agent.version]}"

To prevent accidental overwriting of internal state, two instances of the same Beat running on the same host can no longer share the same data path. To customize the data path for a Beat, use the path.data configuration setting. For example:

path.data: ${path.home}/data-instance1