Falcon LogScale Collector 1.6.2 GA (2024-02-26)
Version? | Type? | Release Date? | Config.Changes? |
---|---|---|---|
1.6.2 | GA | 2024-02-26 | yes |
Hide file download links
Download
Hide file hashes
File | SHA256 Checksum | Hash File |
---|---|---|
linux_amd64.deb | ba2332fac5b6131161380d6ea148fcb2b510d949d39943be42b28b4dbd14a1b8 | |
linux_amd64.rpm | 1eddcefc1e30d17b5f3e8571ade165964c4cd6d5f626bedc655bd3b67ef0291a | |
linux_arm64.deb | f978c49ce790a26bad87ea8faeb6d0b9ea314d06a52c13f314d5a5973386e613 | |
linux_arm64.rpm | 0c551dc50f3bad26dbaf36f7fc5cc84ef49f73c3b373f94e63fd0d50a54b8e4d | |
macOS_universal.pkg | 3339ed432f3e696645920fbc2f39b54983a9c03ed20cf5a34f1ef42972d2ff83 | |
windows_amd64.msi | 343d9aeda9cbaccbfb51a51e257053775a0795f6dec5d7443d9be1d7048cd8df |
Docker Image | Architecture | SHA256 Checksum | Hash File |
---|---|---|---|
logscale-collector:1.6.2 | amd64 | 6d33cb64cc7e6bfb08c6f365735559793b8aa40b631ca6be2a5961e009ee1217 | |
logscale-collector:1.6.2 | arm64 | 6d33cb64cc7e6bfb08c6f365735559793b8aa40b631ca6be2a5961e009ee1217 |
Improvements and bug fixes regarding handling of the file source and installation on Windows.
Improvements, new features and functionality
Collecting Data
The file source now supports environment variable expansions in the include/exclude field in the config.
Bug Fixes
Collecting Data
An requirement has been removed where in previous versions the Windows Event Log source required the existence of at least one channel.
An issue has been resolved when the checkpointing component used by the file source. If a file was rotated/moved while the content was read but not yet acknowledged through the network, the unacknowledged content could be re-transmitted, resulting in duplication of ingest to LogScale.
Other
Fixed a bug where the
--allow-insecure-http
flag would not take effect for communication with Fleet Management. This caused the collector to enforce usinghttps://
for Fleet Management communication even if the enroll command was executed with the--allow-insecure-http
flag.
Installation and Deployment
Installing the Log Collector on Windows using the Windows installer MSI will install it as a service and set the service start setting to
Manual
. After enrolling the Collector into Fleet Management using the enroll command, the service start setting will be set to toAutomatic
. and the service will be started.In previous versions of the installer a new install/upgrade using the installer MSI would set the service start setting to
Manual
. (overriding any current setting), as of 1.6.2 the installer service start setting will be preserved unless you do a fresh install.When performing a new enroll command, You will set the start to
Automatic
option., therefore if you want to set to a custom setting,Automatic (Delayed start)
option. This will need to be done after the enroll command is performed.Note
downgrading to version 1.6.1 or earlier will still revert to the initial setting (
Manual
.).