Beats version 8.17.4
edit
IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.
Beats version 8.17.4
editKnown Issues
editAffecting all Beats
-
Disk queue filled metrics can underflow after blocked publishes. When a disk queue reaches its configured capacity, inputs can block until the output acknowledges events. The queue then accepts the blocked event without updating its metrics. When the event is later removed, the
queue.filled.events,queue.filled.bytes, andqueue.filled.pctmetrics might report incorrect values. Event delivery is unaffected. Upgrade to 8.19.21 or later to apply the fix.
Filebeat
-
The Filestream input does not enforce the restrictions documented for the
clean_inactiveoption, thus allowing configurations that can lead to data re-ingestion issues. -
When
clean_inactive: 0, Filestream cleans the state of all files on start up, effectively re-ingesting all files on restart. Setclean_inactive: -1to disable this behavior.
Breaking changes
editAffecting all Beats
- The Beats logger and file output rotate files when necessary. The beat now forces a file rotation when unexpectedly writing to a file through a symbolic link.
- Allow faccessat(2) in seccomp. 43322
Bugfixes
editFilebeat
- Prevent computer details being returned for user queries by Active Directory Entity Analytics provider. 11818 42796
-
Handle unexpectedEOF error in
aws-s3input and enforce retrying using download failed error. 42420 -
Prevent
azureblobstorageinput from logging key details during blob fetch operations. 43169 - Fixed race conditions in the global ratelimit processor that could drop events or apply rate limiting incorrectly.
Metricbeat
Winlogbeat
- Fix boolean key in security pipelines and sync pipelines with integration. 43027