You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On previous versions, the effective registry path for Ubuntu was /var/lib/filebeat/registry (path.data: /var/lib/filebeat and a relative filebeat.registry.path : registry)
When using the latest 4.11.0 version of this module, filebeat.registry.path is set to /var/lib/filebeat which makes filebeat send en second time all the logs.
Maybe it would be better to keep filebeat's default value and give registry_path an undef value ?
The text was updated successfully, but these errors were encountered:
Impacted version
4.11.0
Description
On previous versions, the effective registry path for Ubuntu was /var/lib/filebeat/registry (path.data: /var/lib/filebeat and a relative filebeat.registry.path : registry)
When using the latest 4.11.0 version of this module, filebeat.registry.path is set to /var/lib/filebeat which makes filebeat send en second time all the logs.
Maybe it would be better to keep filebeat's default value and give registry_path an undef value ?
The text was updated successfully, but these errors were encountered: