Beats version 8.15.4
edit
IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.
Beats version 8.15.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_inactiveto a very large value. For example, useclean_inactive: 43800h0m0s, which is 5 years.
Bugfixes
editAffecting all Beats
- Fix issue where old data could be saved in the memory queue after acknowledgment, increasing memory use. 41356
Filebeat
- Log bad handshake details when websocket connection fails. 41300
- Improve modification time handling for entities and entity deletion logic in the Active Directory entityanalytics input. 41179
-
Fix double encoding of
client_secretin the Entity Analytics input’s Azure Active Directory provider. 41393 - The azure-eventhub input now correctly reports its status to the Elastic Agent on fatal errors. 41469
Metricbeat
- Fix Kubernetes metadata sometimes not being present after startup. 41216
Winlogbeat
- Fix truncated windows event log message. 41327