Falcon LogScale Collector 1.6.5 GA (2024-04-29)

Version^?	Type^?	Release Date^?	Config.Changes^?
1.6.5	GA	2024-04-29	no

Hide file download links

Show file download links

Download

Hide file hashes

Show file hashes

File	SHA256 Checksum	Hash File
linux_amd64.deb	81b54668ead01f8d0cf222035fcf4fa1d287f534152c3799d244e4be5a6b9c43
linux_amd64.rpm	cc36493be196656d87b0412bb414125165331e96415106864d8ca95910befeb6
linux_arm64.deb	b70d5006184c537dcd08fb90c72e6a92d902d3d1d34be014e28d1cb5bbfd1588
linux_arm64.rpm	bdb0fdf05469660c539935ef8191f679215dc21721bbcf1ed9b76eba70b835fc
macOS_universal.pkg	9a4db0cb82398ab5ccf23843b27be80bac853d492b49f0e291b601d8e9eb1ef9
windows_amd64.msi	71a965cd3af6100d9fd3d31ab2661ede3d3bf502fdafb27535c18c24f5c3fac1

Docker Image	Architecture	SHA256 Checksum	Hash File
logscale-collector:1.6.5	amd64	8754dc0cdaead677439bf2a3d1c3150dc2b63ca2f1ec12a0b42a192346e91be4
logscale-collector:1.6.5	arm64	8754dc0cdaead677439bf2a3d1c3150dc2b63ca2f1ec12a0b42a192346e91be4

Improvements and bug fixes regarding handling of the file source.

Improvements, new features and functionality

Debugging
- The error message "Failed sink receive." was previously erroneously logged at Log Collector shutdown, in scenarios where the shutdown was intentional and graceful. This has been corrected.
- On Windows, when file open fails, the error message will now include the path to the file, matching the behaviour on Linux and macOS.
- The error message "Could not identify file." will only be logged once per file that could not be identified. Previously this message would be logged at each failed attempt to identify the file.
- The severity of a number of internal Log Collector log messages has been reduced from error to warning, in cases where the error is already handled.

Bug Fixes

Collecting Data
- A race condition which could cause the Log Collector to crash, when using the static_fields transform, has been identified and addressed.
- In previous versions the file source would hold on to a file handle until the read content was successfully received by LogScale. This could cause the reported disk usage to be higher than expected in scenarios with frequent file-rotation and low bandwidth/loss of connection to LogScale. The Log Collector now releases file handles immediately after reading EOF or detecting files being removed.
- A race condition during file rotation potentially causing the Log Collector to crash has been identified and addressed.
Debugging
- An issue causing the internal debug logging module to log a warning "Dropped debug log message before they enter the ring buffer" has been fixed.
Fleet Management
- Fixed a bug where Log Collector metrics would fail to run, when any of the metrics could not be collected.