Beats version 8.15.5

IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.

Affecting 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, and queue.filled.pct metrics 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_inactive option, 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. Set clean_inactive to a very large value. For example, use clean_inactive: 43800h0m0s, which is 5 years.

Packetbeat

Affecting all Beats

Fix metrics not being ingested, due to "Limit of total fields [10000] has been exceeded while adding new fields […]". The total fields limit has been increased to 12500. No significant performance impact on Elasticsearch is anticipated. 41640

Filebeat