Falcon LogScale 1.161.0 GA (2024-10-22)
Version? | Type? | Release Date? | Availability? | End of Support | Security Updates | Upgrades From? | Config. Changes? |
---|---|---|---|---|---|---|---|
1.161.0 | GA | 2024-10-22 | Cloud | 2025-12-31 | No | 1.112 | No |
Available for download two days after release.
Bug fixes and updates.
Deprecation
Items that have been deprecated and may be removed in a future release.
The lastScheduledSearch field from the
ScheduledSearch
datatype is now deprecated and planned for removal in LogScale version 1.202. The new lastExecuted and lastTriggered fields have been added to theScheduledSearch
datatype to replace lastScheduledSearch.
Upgrades
Changes that may occur or be required during an upgrade.
Installation and Deployment
The JDK has been upgraded to 23.0.1
New features and improvements
UI Changes
A custom dialog now helps users save their widget changes on the
Dashboard
page before continuing on theSearch
page.
Configuration
A new boolean dynamic configuration parameter,
DisableNewRegexEngine
has been added for disabling the LogScale Regular Expression Engine V2 globally on the cluster. This parameter does not stop queries that are already running and using the engine, but prevents the submission of new ones. See Setting a Dynamic Configuration Value for an example of how to set dynamic configurations.
Dashboards and Widgets
The
Bar Chart
widget can now be configured in the style panel with a horizontal or vertical orientation.
Functions
The new query functions
crypto:sha1()
andcrypto:sha256()
have been added. These functions compute a cryptographic SHA-hashing of the given fields and output ahex
string as the result.
Fixed in this release
Storage
Mini-segments would not be prioritized correctly when fetching them from bucket storage. This issue has now been fixed.
Dashboards and Widgets
Long values rendered in the
Single Value
widget would overflow the widget container. This issue has now been fixed.
Queries
The query scheduler has been fixed for an issue that could cause queries to get stuck in rare cases.
Improvement
UI Changes
Improving the information messages that are displayed in the query editor when errors with lookup files used in queries occur.
Queries
Worker query prioritization is improved in specific cases where a query starts off highly resource-consuming but becomes more efficient as it progresses. In such cases, the scheduler could severely penalize the query, leading to it being unfairly deprioritized.