Falcon LogScale 1.124.0 Preview (2024-02-06)
|End of Support
|Req. Data Migration
Bug fixes and updates.
The following items are due to change in a future release.
Items that have been deprecated and may be removed in a future release.
In the GraphQL API, the name argument to the parser field on the
Repositorydatatype has been deprecated and will be removed in version 1.136 of LogScale.
We are deprecating the
humio/zookeeperDocker images due to low use. The planned final release for these images will be with LogScale 1.148.0.
Better alternatives are available going forward. We recommend the following:
If you still require
humio/zookeeperfor needs that cannot be covered by these alternatives, please contact Support and share your concerns.
humioDocker image is deprecated in favor of
humiois no longer considered suitable for production use, as it runs Kafka and Zookeeper on the same host as LogScale, which our deployment guidelines no longer recommend. The final release of
humioDocker image will be in version 1.130.0.
humio-single-node-demoimage is an all-in-one container suitable for quick and easy demonstration setups, but which is entirely unsupported for production use.
For more information, see LogScale Docker Core Container.
Scripts or environment which make use of these tools should be checked and updated for the new configuration:
We have adjusted the code that calculates where to start reading from the ingest queue to be more conservative. It will no longer allow for skipping past segments that are not fully replicated when later segments on the same datasource are fully replicated. This fixes a very rare edge case that could cause data loss on clusters using ephemeral disks. Due to the changed behavior, any segment failing to properly replicate will now cause LogScale to stop deleting data from the affected Kafka partition. Cluster administrators are strongly encouraged to monitor this case, by keeping under observation Kafka's disk usage.
Improvements, new features and functionality
Multi-Cluster Search — early adopter release for Self-hosted LogScale.
Keep the data close to the source, search from single UI
Search across multiple LogScale clusters in a single view
Support key functionalities like alerts & dashboards
The functionality is limited to LogScale self-hosted versions at this point.
For more information, see LogScale Multi-Cluster Search.
The Field Aliasing feature is introduced. Implementing Field Aliasing in your workflow simplifies data correlation from various sources. With this feature, users can give alternative names — aliases — to fields created at parse time, across a view, or the entire organization. It makes data interpretation more intuitive and provides analysts with a smoother search experience.
For more information, see Field Aliasing.
Fixed an issue that could cause repositories undeleted using the mechanism described at Restoring a Repository or View to be only partially restored. Some deleted datasources within the repositories could erroneously be skipped during restoration.
For more information, see Restoring a Repository or View.
Allowed reassignment of digest that assigns partitions unevenly to hosts. This is to support clusters where hosts are not evenly sized, and so an even partition assignment is not expected.