Latest GA Release
Falcon LogScale 1.194.0 GA (2025-06-24)
Version? | Type? | Release Date? | Availability? | End of Support | Security Updates | Upgrades From? | Downgrades To? | Config. Changes? |
---|---|---|---|---|---|---|---|---|
1.194.0 | GA | 2025-06-24 | Cloud | Next LTS | No | 1.150.0 | 1.177.0 | No |
Available for download two days after release.
Hide file download links
Download
Use docker pull humio/humio-core:1.194.0 to download the latest version
Advance Warning
The following items are due to change in a future release.
Functions
Starting from release 1.195, the query functions
asn()
andipLocation()
will display an error instead of a warning should an error occur with their external dependency. This change will align their behavior to functions using similar external resources, likematch()
,iocLookup()
, andcidr()
.
Deprecation
Items that have been deprecated and may be removed in a future release.
The
color
field on theRole
type has been marked as deprecated (will be removed in version 1.195).The setConsideredAliveUntil and
setConsideredAliveFor
GraphQL mutations are deprecated and will be removed in 1.195.The
lastScheduledSearch
field from theScheduledSearch
datatype is now deprecated and planned for removal in LogScale version 1.202. The newlastExecuted
andlastTriggered
fields have been added to theScheduledSearch
datatype to replacelastScheduledSearch
.The
EXTRA_KAFKA_CONFIGS_FILE
configuration variable has been deprecated and planned to be removed no earlier than version 1.225.0. For more information, see RN Issue.
rdns()
has been deprecated and will be removed in version 1.249. UsereverseDns()
as an alternative function.The updateScheduledSearchV2 GraphQL mutation has been deprecated in favor of updateScheduledSearchV3, which now includes field triggerOnEmptyResult.
New features and improvements
Automation and Alerts
Scheduled searches can now trigger actions even when no results are found. Previously, actions would only trigger when results were found. This is an optional feature that you can set in Advanced settings.
It is now possible to test Actions with an empty set of events. This feature allows for validating that actions work correctly when no events are found by a scheduled search, and helps prevent action configuration errors.
GraphQL API
Added the ability to create a saved query from a yaml template via the new createSavedQueryFromTemplate GraphQL mutation.
Configuration
The new configuration option
QUERY_SCHEDULER_QUERY_QUEUE_SIZE
now determines the number of queries that can be enqueued on the query workers while waiting to start running.Introduced a configurable limit on the number of connections that can be attached to a Multi-Cluster View . The default limit is 50, but can be changed through the environment variable
MAX_FEDERATED_CONNECTIONS
.Introduced a configurable limit on the number of tags that can be added to a Multi-Cluster View connection. The default limit is 25, but can be changed through the environment variable
MAX_FEDERATED_CONNECTION_TAGS
.
Fixed in this release
Administration and Management
Fixed an issue in the live-dashboard-query-count metric to improve accuracy.
User Interface
Fixed an issue where some table columns would not get sorted properly.
Dashboards and Widgets
Widgets now display the
Raw
value format with better precision, as they no longer round/truncate significant digits: instead, raw values now keep the same precision that JavaScript floats can handle. For example, before the fix a chart would display a raw value format like 12345678 as 12,345,700; after the fix, the chart correctly displays the value as 12,345,678.
Queries
Fixed an issue where during digest restart a query might receive duplicate events.
Improvement
Storage
Made improvements to all bucket upload operations. Bucket storage upload operations (uploaded files/global snapshots/segments) now work more efficiently by utilizing the upload queue and callback functions to complete the upload. This ensures that configured concurrency limits are properly enforced.
Functions
The
correlate()
function now generates a warning message when used in an unsupported, non-top-level context, such as in subqueries or when passed as an argument to a function.